Forum Moderators: phranque

Message Too Old, No Replies

HTTP/1.0 blocking

         

Mr_Sinister

11:13 pm on Mar 11, 2009 (gmt 0)

10+ Year Member



Hi, I run a small chat room for a few friends, and someone is using a HTTP/1.0 proxy server to spam us. I can't block via. IP address because it changes frequently, and I can't figure out how to block HTTP/1.0 requests (all the "good" requests use HTTP/1.1).

Could someone tell me how to do this?

g1smd

11:25 pm on Mar 11, 2009 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



Look at THE_REQUEST.

This was discussed just a couple of hours ago: [webmasterworld.com...]

Are there any search engine bots still issuing HTTP/1.0 requests?

jdMorgan

12:56 am on Mar 12, 2009 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



Yes and no... Many search engines send "HTTP/1.0" at the end of the request header, but they also send an HTTP Host header -- and that header was not defined until HTTP/1.1. So, we call those user-agents' requests "Extended HTTP/1.0 requests."

The intent is to be HTTP/1.0 compatible so that they can spider very old servers, but to provide the Host header required by HTTP/1.1 to support multiple domains sharing the same IP address (which isn't possible using strict HTTP/1.0 -- which resolves a domain to a server by IP address only, and does not send the client-requested domain name to the server at all).

In the case at hand, blocking by the presence of HTTP/1.0 at the end of THE_REQUEST won't be sufficient because legitimate search spiders such as Yahoo! Slurp will be blocked. A combination of user-agent and HTTP/1.0 presence may be enough if this "user" is not switching user-agents dramatically. If he is, then perhaps block with (THE_REQUEST ends with HTTP/1.0) and (HTTP_USER_AGENT is NOT a search engine spider).

Jim

Key_Master

1:15 am on Mar 12, 2009 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



You can also use SetEnvIf directive and the Request_Protocol attribute to block HTTP 1.0 requests. You wouldn't need any complicated rewrites and it would be fairly easy to allow access to good bots that still make HTTP 1.0 requests.

wilderness

2:52 am on Mar 12, 2009 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



Could someone tell me how to do this?

A possibility that you may accomplish what you desire in reverse?

Rather than seeking to deny somebody unknown?

Simply deny everybody and only allow access to the IP ranges of the known IP's (i. e.,"few friends").
This basically amounts to password protected zone and you'll need to make participants aware of the requirements OUTSIDE of the open forum.