Note! ApacheBench (ab) is installed on macOS by default. You can check that by using ab -h [for help/information] [for checking ab version] ab -V Ref: https://vyspiansky.github.io/2019/12/02/apache-bench-for-load-testing/
Here you go: import org.apache.commons.codec.binary.Base64; @Test public void testDecodeJWT(){ String jwtToken = “eyJhbGciOiJIUzI1NiJ9.eyJzdWIiOiJ0ZXN0Iiwicm9sZXMiOiJST0xFX0FETUlOIiwiaXNzIjoibXlzZWxmIiwiZXhwIjoxNDcxMDg2MzgxfQ.1EI2haSz9aMsHjFUXNVz2Z4mtC0nMdZo6bo3-x-aRpw”; System.out.println(“———— Decode JWT ————“); String[] split_string = jwtToken.split(“\\.”); String base64EncodedHeader = split_string[0]; String base64EncodedBody = split_string[1]; String base64EncodedSignature = split_string[2]; System.out.println(“~~~~~~~~~ JWT Header ~~~~~~~”); Base64 base64Url = new Base64(true); String header = new String(base64Url.decode(base64EncodedHeader)); System.out.println(“JWT Header : ” + header); System.out.println(“~~~~~~~~~ JWT … Read more
(I tried $1%20$2 at the end, which also went badly). This looks like a bug. Encoding the space as %20 in the query string should be valid. You can also encode the space as + in the query string (as in your workaround). In your original rule, Apache should be encoding the space (as %20) … Read more
Evolving schemas Suppose intially you designed an schema like this for your Employee class { {“name”: “emp_name”, “type”:”string”}, {“name”:”dob”, “type”:”string”}, {“name”:”age”, “type”:”int”} } Later you realized that age is redundant and removed it from the schema. { {“name”: “emp_name”, “type”:”string”}, {“name”:”dob”, “type”:”string”} } What about the records that were serialized and stored before this schema … Read more
Use Alias: Alias /ABC/ /var/www/ABC/ Alias /PQR/ /var/www/PQR/ Leave the document root pointing to /var/www/Others/index.php. It could do the trick. 🙂
The normal operation of apache/mod_rewrite doesn’t work like this, as it seems to turn the plus signs into spaces. I don’t think that’s quite what’s happening. Apache is decoding the %2Bs to +s in the path part since + is a valid character there. It does this before letting mod_rewrite look at the request. So … Read more
From an answer on Quora by Jonathan Klein, 12ms for a 1500 line .htaccess file: Having a large .htaccess does have a cost. Ours is currently ~1500 lines and we benchmarked the time spent parsing it at around 10-12ms on a production webserver. Hardware makes a difference obviously, but you can fairly safely assume that … Read more