httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Randy Terbush <ra...@zyzzyva.com>
Subject AOL == problem
Date Thu, 19 Dec 1996 23:49:13 GMT

> > > On Wed, 18 Dec 1996, Randy Terbush wrote:
> > > 
> > > > Some more tidbits on this since I have battled it most of the day.
> > > > 
> > > > I have found that even though Apache logs a 200 on a request,
> > > > the AOL browser is getting the infamous message stating that there
> > > > is a problem  with the webserver. I would *love* to know what these
> > > > guys are up to. My bet is no good...
> > > 
> > > Alexei sez:
> > > Well, FWIW, it makes perfect sense that Apache would log a 200. After
> > > all, as far as Apache is concerned, it's done nothing wrong... it's
> > > just sent a normal response. It's the AOL browser or proxy that's
> > > screwed up with what to do with it.
> > 
> > Randy sez:
> > Agreed. There is more going on here than just the protocol version
> > as near as I can tell. I hacked in code to do a browser match for
> > AOL 3.0 and send a HTTP/1.0 response. Still doesn't fix the problem.
> 
> Andrew sez:
> Does AOL like Apache 1.1.1 ?  If so then hack the version up to
> Apache/1.2b... and see if it breaks.  You might be seeing the side
> effect of some other 1.2b specific behaviour confusing the proxies
> (ETag?), but it might be something as crude as the proxy abusing
> the server software version.  In which case, hem...
> 
> Ay.


Hmmm. As I dug into this, I wondered about Etag:. 

I'll go upgrade a 1.1.1 server now.... :)





Mime
View raw message