Ukstokes.com

[...] a nice 404 page. Instead we will catch them on the Apache layer and display a static 404 error page so that Tomcat can carry on with serving the important traffic. Creating a custom 404 error [...]

[...] I’ve been having a bit of fun this week Apache rewrite rules based on cookie values. The problem I had to fix was unintended redirects because of [...]

[...] this but this is how I did it, by setting an environment variable called %{SCHEME} using rewrite rules: After that just amend your LogFormat definition to include url_scheme=”%{SCHEME}e& [...]

[...] do the same thing as commenting/uncommenting the LoadModule lines. 2. Obfuscate your Server header. An attacker that doesn’t know what webserver or app server you are running is far less [...]

[...] be enabled by default. In Ubuntu just run a2enmod to enable the module. You can also chuck a rewrite rule in there if you want users to land on a specific URI when they hit the document root. [...]

[...] will then become your Apache server’s default 404 error page. The last step is to add a rewrite rule to cover some of the common file extensions that hackers look for. You can do this using a [...]

[...] large organisation the topology will probably be many Tomcat instances (maybe hundreds), few Apache servers (probably less than 10), and a single load balancer in front of the Apache servers. So [...]

[...] jk unmount it: Once you have reloaded your Apache configuration, this will then become your Apache server’s default 404 error page. The last step is to add a rewrite rule to cover some of the [...]

[...] in the case of these brute force URL attacks we don’t want to waste CPU cycles on the Tomcat server rendering a nice 404 page. Instead we will catch them on the Apache layer and display a static [...]