New answers tagged

0

These happen all the time. I see this at least a dozen times a day in my server logs. Best bet is to block the connection from coming in at the firewall or gateway and that way it doesn't hit your server, otherwise if it isn't a big deal for you and isn't causing you too many hassles and you aren't seeing other errors in relation to this connection then you ...


1

The other answers have already covered that redirecting would be a bad/pointless response and that simply dropping the response with a suitable status would be preferred. However, you did ask some other questions... will the other destination be aware of my Server IP? You used Google in your example. Being a search engine they will probably discover ...


5

Well aren't you friendly... "Hey Google, I'm having a DOS, but im making it your problem, thanks" First: There is no difference for you between serving an 301 or an 404 error page. Your server will have to do the same amount of work. The difference here is that you, with your 301->google solution, now ALSO make it Google's problem, effectively doubling ...


0

In the situation you give it is definarely dangerous and not a good idea, and could most definately result in issues for your site, it woukd be better to simply take that one file offline or if the traffic is coming from one cidr block then block that cidr, forwarding the attack to another site oike Google could ge seen as you taking part in the attack, plus ...


4

how this workaround indeed works PHP runs later in the request, so most of the time you can simply override any headers that Apache has already set in your PHP code. That's pretty much it. (Aside: Sending 403s through your 404 handler in this way obviously makes it harder to trigger a real 403 from your Apache config/.htaccess, if you should need to.) ...



Top 50 recent answers are included