- From: Fish <fish@infidels.org>
- Date: Fri, 1 Sep 2000 21:08:15 -0700
- To: <www-talk@w3.org>
I respectfully disagree. While RFC 2616 doesn't mention specifically how to handle such a situation, it does mention that the order of individual field values for a given header *is* significant. Thus I would think that common sense would prevail in such a situation and the each subsequent new occurrence of given field value would override any previous value so in the example Jim provided, "keepalive" would override (i.e. replace) the previously supplied "close" value. Think of it as the server "changing its mind." It first decides the connection should be closed at the end of this response, and then a moment later, decides the connection should be kept open afterall but due to a bug has already emitted a "Connection:close" header. "Fish" (David B. Trout) fish@infidels.org "Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning." - Rich Cook > -----Original Message----- > From: www-talk-request@w3.org [mailto:www-talk-request@w3.org]On Behalf > Of Nic Ferrier > Sent: Friday, September 01, 2000 9:31 AM > To: www-talk@w3.org > Subject: Re: Msg Header content > > > >>> Jim Witt <JWitt@ECCubed.com> 01-Sep-00 4:43:51 PM >>> > > >I receive responses such as the following from a web server: > > HTTP/1.1 200 OK > > Server: Netscape-Enterprise/4.0 > > Date: Wed, 30 Aug 2000 19:02:26 GMT > > Content-length: 148 > > Content-type: image/gif > > Connection: Close > > Connection: keep-alive > > > >Q: Is the following legal as part of a response header? > > Connection: Close > > Connection: keep-alive > > No... but a client should handle it properly (close the connection). > > Are you by any chance using a servlet engine attached to that > webserver? > > > Nic
Received on Saturday, 2 September 2000 00:08:27 UTC