1.1b4 bug with ErrorDocument (fwd)

[Rob Hartill <ro...@imdb.com>]

more nonsense ?

not acked



From: Ingo Macherius <in...@mwe.hvr.scn.de>
Message-Id: <19...@ESAMX6.mwe.hvr.scn.de>
Subject: 1.1b4 bug with ErrorDocument
To: apache-bugs@apache.org
Date: Wed, 19 Jun 1996 20:44:42 +0200 (MDT)
Cc: webmaster@mwe.hvr.scn.de
Reply-To: Ingo Macherius <In...@mwe.hvr.scn.de>
Organisation: Siemens AG Hannover, TD MWE
X-URL: http://www.tu-clausthal.de/~inim
X-Mailer: ELM [version 2.4 PL24alpha5]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 2132      

-----BEGIN PGP SIGNED MESSAGE-----


Sender:         Ingo Macherius  <In...@mwe.hvr.scn.de>
Problem:        ErrorDocument uses outdated cache document
OS:             Sinix 5.41, which is a straight AT&T SVR4 derivate
		Linux 2.0.0 
Apache Version: 1.1b4
Extra Modules:  mod_proxy.c http_protocol.c
Disclaimer:	You can't check the quoted URLs because this is a
		Server within Siemens Intranet :-(
Symtoms:        

I use the ErrorDocument directive to point to static custom error handling
pages in German language.
Our Proxy-Server (apache 1.1b4) points srm.conf has the following entry:

	# NEW config
    ErrorDocument 400 http://www.mwe.hvr.scn.de/admin/errors/proxy/400.html
	[...]
    ErrorDocument 503 http://www.mwe.hvr.scn.de/admin/errors/proxy/503.html

formerly this was

	# OLD config
    ErrorDocument 400 http://www.mwe.hvr.scn.de/errors/proxy/400.html
        [...]
    ErrorDocument 503 http://www.mwe.hvr.scn.de/errors/proxy/503.html

Due to (shame) misconfiguration the proxy (www-proxy.mwe.hvr.scn.de)
cached our own server (www.mwe.hvr.scn.de). So the old error pages
were cached.

I found this bug because of the following situation:
The OLD srm.conf was still active, but the pages were already moved
to the NEW location. The OLD URL's did no longer exists.

I provoked an error 403 and found myself with the OLD error document.
This can only be coming from the caching proxy, as the file no longer
exists.

Conclusion:	Before getting ErrorDocuments a http
		If-Modified-Since request should be sent to prevent
		usage of outdated/non-existant error handlers.

Virtually yours,
Ingo
- -- 
Campus:  Ingo.Macherius@tu-clausthal.de      http://www.tu-clausthal.de/~inim
Siemens: Ingo.Macherius@mwe.hvr.scn.de       http://www.scn.de/~inim
 information != knowledge != wisdom != truth != beauty != music == best (FZ)

-----BEGIN PGP SIGNATURE-----
Version: 2.6

iQCVAwUBMchKiWqfQvFsxpv9AQEXpgQArUeffVMLqf0Kz/17Nk1pKqEiHeWxOvtL
IirOyQVFibCBVLnBf0s+j/mwSap6d63QUW6P4P0QSJDULrbmC5hkx/b/vF8IoyOL
Hbi4JZhd4ilsDimduplK2RpZ9mfRkKJGpbv0yL6uLMAVeToBzyIFJS6Dl5pEyN17
Iou1/NKHjnQ=
=THcP
-----END PGP SIGNATURE-----
----- End of forwarded message from Ingo Macherius -----

-- 
Rob Hartill (robh@imdb.com)
The Internet Movie Database (IMDb)  http://www.imdb.com/
           ...more movie info than you can poke a stick at.

Re: 1.1b4 bug with ErrorDocument (fwd)

[Alexei Kosut <ak...@organic.com>]

On Wed, 19 Jun 1996, Rob Hartill wrote:

> more nonsense ?

Yes, it's nonsense. He's pointing his error documents at remote documents
that return 200 responses (I think), so of course they're getting
cached. The proxy server's doing exactly what it's told. I think that's
it, at least. I'm not really sure what exactly he's talking about.

Of course, this goes back to the argument we had a few months ago over
whether or not the proxy server should always do a conditional GET, even
if it had decided the document (one w/o an Expires header) was "fresh".

Anyhow...

-- Alexei Kosut <ak...@organic.com>            The Apache HTTP Server 
   http://www.nueva.pvt.k12.ca.us/~akosut/      http://www.apache.org/