Re: IE 4.0 Problem?

In article <34559505.13F2C0E4@beam.com.au> you write:

>My cache.log is generating of lot of errors very similar to the
>following:
>
>-------------
>97/10/20 23:51:54| icpDetectClientClose: FD 14, 255 unexpected bytes
>97/10/20 23:51:54| --> from: XXX.XX.XXX.XXX
>97/10/20 23:51:54| --> data:
>GET%20http://www.hotwired.com/livewired/objects/wiredChannelGuide/wired.ico%20HTTP/1.0%0d%0aAccept:%20*/*%0d%0aUser-Agent:%20Mozilla/4.0%20(compatible;%20MSIE%204.0;%20MSIECrawler;%20Windows%2095)%0d%0aAccept-Language:%20en-au%0d%0aAccept-Encoding:%20gzip,%20deflate%0d%0aHost:%20www.hotwired.com%0d%0aProxy
>-------------

Mine too :-(.

>From what I can work out, all these errors are generated from machines
>that are running that stupid Internet Explorer 4.0.... Is anyone else

Yep.

>encountering this problem? If so, how can I stop it happening? Why is
>it happening? It occurs on any site, not just the hotwired example

IE 4.0 sends a HTTP/1.0 request with a 'Proxy-Connection: Keep-Alive'
header. I've looked briefly in the HTTP/1.1 RFC's (2068 and 2145) and I
think it's like this:

Keep-alive connections are not default for HTTP/1.0 but *are* for
HTTP/1.1. In case keep-alive is used with HTTP/1.0 requests (and answers)
both sides must include Proxy-Connection: headers. Squid does not send a
Proxy-Connection: header back so IE 4.0 should stop treating the
connection as a keep-alive connection (AFAIK), but it doesn't and Squid
gets unwanted data from the second request on that connection.

A colleague told me that there are HTTP/1.1 and HTTP/1.1-proxy switches in
IE 4.0 but haven't experimented with those yet.

Arjan
Received on Tue Oct 28 1997 - 10:18:26 MST