Gary Armstrong wrote:
>
>
> Davide Bianchi wrote:
>
>> Gary Armstrong <garyarm.RemoveThis@testedgeinc.com> wrote:
>>
>>> I've noticed a couple of entries in my access log that look like this:
>>> 61.144.100.66 - - [31/Jul/2003:13:51:43 -0700] "GET
>>> <a style='text-decoration: underline;' href="http://www.alltheweb.com/" target="_blank">http://www.alltheweb.com/</a> HTTP/1.1" 200 294
>>
>>
>>
>> Someone is using your system as an open proxy. Check that he can't
>> be done and add that IP to your firewall.
>>
>> Davide
>
>
> That is what I feared. Looking at httpd.conf, I see:
>
> #ProxyRequests On
>
> This line is commented out and the doc states that, I should uncomment
> it too turn on the proxy server. Yet the access log shows the server
> returned 200. What Am I missing?
>
Ah well, it means they can still TRY to use ite as an open proxy, but it doesn't mean they succeed with it. Someone is probably just scanning a whole lot of ip adresses in order to find someone as stupid as I once was. Trust me, if you have an open proxy, your internet connection will soon be flooded and you WILL notice. If you have only a few of those entries in your log files, don't worry about it.
<rip>
+ <p>If your server is configured properly, then the attempt to
+ proxy through your server will fail. If you see a status
+ code of <code>404</code> (file not found) in the log, then
+ you know that the request failed. If you see a status code
+ of <code>200</code> (success), that does not necessarily mean
+ that the attempt to proxy succeeded. RFC2616 section 5.1.2
+ mandates that Apache must accept requests with absolute URLs
+ in the request-URI, even for non-proxy requests. Since
+ Apache has no way to know all the different names that your
+ server may be known under, it cannot simply reject hostnames
+ it does not recognize. Instead, it will serve requests for
+ unknown sites locally by stripping off the hostname and using
+ the default server or virtual host. Therefore you can
+ compare the size of the file (1456 in the above example) to
+ the size of the corresponding file in your default server.
+ If they are the same, then the proxy attempt failed, since a
+ document from your server was delivered, not a document from
+ <code>www.yahoo.com</code>.</p>
</rip>
i.e. instead of serving <a style='text-decoration: underline;' href="http://www.alltheweb.com/" target="_blank">http://www.alltheweb.com/</a> through a proxy, apache served <a style='text-decoration: underline;' href="http://www.yourdomain.com/" target="_blank">http://www.yourdomain.com/</a> with status 400.
Michiel.<!-- ~MESSAGE_AFTER~ -->
>> Stay informed about: Access log?