httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jim Jagielski <...@jaguNET.com>
Subject Re: HTTP/1.1 header problem (fwd)
Date Sat, 21 Dec 1996 03:23:50 GMT
sameer wrote:
>
>  yah know I think we might be wrong. I'm reading the 1.0 spec:
>
> HTTP/1.0 clients must:
>
>      recognize the format of the Status-Line for HTTP/1.0 responses;        
>      understand any valid response in the format of HTTP/0.9 or HTTP/1.0.   
>
>  That looks like if we send http/1.1 they can bail if they want.
>
>  I haven't read the whole spec, mind you.
>
>  Isn't Roy our local HTTP cop? What does Roy have to say? I hope he isn't on
> vacation or something.
>
>
> > >----- Forwarded message from George Boyce -----
> > >
> > >
> > >4. But a recent version of the apache server does send HTTP/1.1 headers
> > >even when contacted by a HTTP/1.0 browser and proxy. After careful
> > >thought and loud debate, I lost, and we consider this to be inconsistent
> > >with the HTTP/1.0 spec.  We also consider our error message to be
> > >consistent with the HTTP/1.1 spec, though our service is certainly not
> > >HTTP/1.1 compliant, and of course it isn't very friendly to our members.
> > >
> > >The 1.0 spec doesn't allow the server to respond with a 1.1 response:
> > >
> > >http://www.w3.org/pub/WWW/Protocols/HTTP/1.0/spec.html << HTTP/1.0
> > >servers must:
> > >.........................................................................
> > >     respond appropriately with a message in the same protocol version
> > >used by the client.
> > >

Ahhh.... but 1.2b? is NOT a HTTP/1.0 server. My reading of the spec
is that 1.1 servers can, and should, respond to 1.0 requests with
a 1.1 response. 

-- 
====================================================================
      Jim Jagielski            |       jaguNET Access Services
     jim@jaguNET.com           |       http://www.jaguNET.com/
                  "Not the Craw... the CRAW!"

Mime
View raw message