Thanks for your help.

On Sat, Mar 1, 2008 at 11:42 AM, Amos Jeffries  wrote:
>  I'm not sure what you mean by this?
>  The error response and page as a whole _replaces_ the
>  original URL and  page requested _as a whole_.

Well, if I compose an HTML page to replace ERR_ACCESS_DENIED, and the
page has an IMG tag which refers to "images/logo.jpg", then apache
assumes that the location of the logo.jpg file is on the server to
which I was attempting to connect before my access was denied.

So if I was attempting to view http://www.cricinfo.com, apache assumes
that the location of the file "logo.jpg" is at
http://www.cricinfo.com/images/logo.jpg and returns a "404"

If the IMG tag is changed to "http://localhost/images/logo.jpg"; the
result is the same.

If, however, the IMG tag is changed to
"http://192.168.60.254/images/logo.jpg"; the result is slightly
different: the /var/log/apache2/access.log file reveals that apache
believes a dummy file has been requested and returns 200.

127.0.0.1 - - [01/Mar/2008:11:52:32 +0200] "GET / HTTP/1.0" 200 738
"-" "Apache/2.2.4 (Ubuntu) PHP/5.2.3-1ubuntu6 (internal dummy
connection)"

It may be that Apache is at fault here, and I will research this.

But my gut feel is that Squid is spoofing the location of the
ERR_ACCESS_DENIED file as being on the server of the requested URL.

This is not a big deal as far as the "images/logo.jpg" is concerned,
but it drives a coach and horses through my idea to call a perl cgi
script from the ERR_ACCESS_DENIED page.

Reply via email to