Re:The long and sordid history of the user-agent HTTP header...
by jackalope on Sunday July 15, 2012 @04:42PM
(#4248039)
I return a 403 if User-Agent or Host headers are missing. And my firewall will lock you out completely if you use "User-agent" instead of "User-Agent" (among many other obvious giveaways in the User-Agent header).
[ Parent
| on HN ]
Re:The long and sordid history of the user-agent HTTP header...
by icebraining on Sunday July 15, 2012 @06:08PM
(#4248341)
Why?
Re:The long and sordid history of the user-agent HTTP header...
by jackalope on Sunday July 15, 2012 @09:34PM
(#4248919)
I block anything that looks like penetration testing or content scraping if there's no chance of false positives. Even when there's no vulnerability present, it conserves resources on dynamically generated sites.
Re:The long and sordid history of the user-agent HTTP header...
by dredmorbius on Monday July 16, 2012 @11:27AM
(#4251079)
Why I can appreciate that, why not block based on patterns of use rather than headers?