> The server header gives more information but what's displayed in the xhtml > body > of the 403 response is "nginx" only which is what will be displayed in the > user > www browser, and that's mis-leading and unfair for nginx. Maybe somebody > should contact CloudFlare to make them modify their response bodies from stock > nginx.
When cloudflare blocks a user-agent, its because the cloudflare customer configured it to do so. Contact the customer, not cloudflare. Also, when cloudflare emits a 403 error, the error page is *ALWAYS* cloudflare branded. Also see: https://support.cloudflare.com/hc/en-us/articles/200169226-Why-am-I-getting-a-403-error- That is however not the case with rawstory.com. Therefor: - rawstory.com uses cloudflare, but - cloudflare does not block lynx in this instance - the backend (rawstory.com) nginx server blocks the user-agent There is no one to blame other than the original host. Lukas _______________________________________________ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx
