RE: IE5 errordocument handling

[Randy Terbush <ra...@covalent.net>]

Thanks. I've forwarded this to our development mailing list.

> -----Original Message-----
> From: rich@hydra4.trl.oz.au 
> [mailto:rich@hydra4.trl.oz.au]On Behalf Of
> Richard Horwood
> Sent: Thursday, August 26, 1999 6:51 PM
> To: gavin@libertyone.com.au; andrew@mondial.com.au
> Cc: apache@apache.org
> Subject: 
> 
> 
> Lo there.
> 
> I've written a small patch for Apache that gets around the 
> problem with IE5
> generating its own pages on "404 Not Found" errors (amongst 
> others).  The
> problem with this is that is screws up any ErrorDocument 
> directive you may have
> defined for your web server.  Instead of actually providing 
> useful information
> to customers/users, IE5 totally ignores it and supplies its 
> own page.
> 
> We get around this by fooling IE5 into thinking that a '404 
> Not Found' is
> actually a '200 OK', and thus displays the ErrorDocument as 
> configured by the
> web server.
> 
> Not exactly kosher, but then this *is* Microsoft we're 
> dealing with :)
> 
> If a request is made by a non-IE5 browser, or there is no 
> ErrorDocument
> defined for the server, Apache continues as normal.
> 
> Enjoy :)
> 
> -Rich.
> 

Re: IE5 errordocument handling (4/5/1999)

[tser <te...@worldonline.nl>]

i digged in the archive:

At 4/5/1999, Dean Commented on it :
[..."And that we should pad custom error messages to 513 bytes for all
responses..."]

Hopes that helps,
	Regards,
	Reinder Kraaij

RE: IE5 errordocument handling

["R.J. Kraaij" <te...@worldonline.nl>]

Let us pray there are no proxy's in the world based on the ie5 engine...

If, Once, in a while, somebody, is using a proxy, which fakes that he's
ie5, or, actualy , is , using the ie5 engine, this solution might give a
lot of unwanted results.

And Yes..i was running one of our caches, faking around the world that he
was ie5, so there might be others fools like me around.

I think staying at 404, and enlarging the response over the (300bytes was
it ?) bytes, so that ie5 understands that there realy is a helpfull
documentcoming is a better solution, then reporting a 200 OK.

i vaguely remember a discussion about this, some months ago.


 - Reinder Kraaij.



On Sun, 29 Aug 1999, Randy Terbush wrote:

> Thanks. I've forwarded this to our development mailing list.
> 
> > -----Original Message-----
> > From: rich@hydra4.trl.oz.au 
> > [mailto:rich@hydra4.trl.oz.au]On Behalf Of
> > Richard Horwood
> > Sent: Thursday, August 26, 1999 6:51 PM
> > To: gavin@libertyone.com.au; andrew@mondial.com.au
> > Cc: apache@apache.org
> > Subject: 
> > 
> > 
> > Lo there.
> > 
> > I've written a small patch for Apache that gets around the 
> > problem with IE5
> > generating its own pages on "404 Not Found" errors (amongst 
> > others).  The
> > problem with this is that is screws up any ErrorDocument 
> > directive you may have
> > defined for your web server.  Instead of actually providing 
> > useful information
> > to customers/users, IE5 totally ignores it and supplies its 
> > own page.
> > 
> > We get around this by fooling IE5 into thinking that a '404 
> > Not Found' is
> > actually a '200 OK', and thus displays the ErrorDocument as 
> > configured by the
> > web server.
> > 
> > Not exactly kosher, but then this *is* Microsoft we're 
> > dealing with :)
> > 
> > If a request is made by a non-IE5 browser, or there is no 
> > ErrorDocument
> > defined for the server, Apache continues as normal.
> > 
> > Enjoy :)
> > 
> > -Rich.
> > 
>