search

kyprizel / testcookie-nginx-module

simple robot mitigation module using cookie based challenge/response technique. Not supported any more.
http://kyprizel.github.com/testcookie-nginx-module/
525 stars 140 forks source link

Send 503 error instead of 200 ok #19

Closed ramilexe closed 8 years ago

ramilexe commented 10 years ago

When module is enable it modify content but send 200 ok. It is bad for SEO. I suggest send 503 temporary unavailable for search bot come back later and didn't index bad content.

infinitnet commented 10 years ago

Why not send (or not send) a 444 status code to reduce the load on NGINX further, because it doesn't have to send a reponse at all to the bad bots? Maybe it would make sense to add a new option "testcookie.status = XYZ".

On 22.08.2014 01:33, Ramil wrote:

When module is enable it modify content but send 200 ok. It is bad for SEO. I suggest send 503 temporary unavailable for search bot come back later and didn't index bad content.

    You can merge this Pull Request by running

git pull https://github.com/ramilexe/testcookie-nginx-module master

Or view, comment on, or merge it at:

https://github.com/kyprizel/testcookie-nginx-module/pull/19

    Commit Summary

— Reply to this email directly or view it on GitHub https://github.com/kyprizel/testcookie-nginx-module/pull/19.

ramilexe commented 10 years ago

When occur first request you don't know bot it or not. If you send 200 ok it will be bad for SEO because you content only to check bot () So I suggest return 503 to say search engines not process this response.

ramilexe commented 8 years ago

@kyprizel it took long time)

kyprizel commented 8 years ago

sorry :) added testcookie_refresh_status instead