- From: Simon Spero <ses@tipper.oit.unc.edu>
- Date: Tue, 31 Dec 1996 09:03:29 -0500 (EST)
- To: sameer <sameer@c2.net>
- Cc: abigail@ny.fnx.com, brian@organic.com, hedlund@best.com, dmk@research.bell-labs.com, http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com, www-talk@www10.w3.org
On Mon, 30 Dec 1996, sameer wrote: > > HTTP/1.7, etc responses. That of course means no HTTP/1.x header can > > ever contain something which causes problems with HTTP/1.0 clients. > That's correct. That *is* why it's called HTTP/1.x, and not > HTTP/2.x This is indeed the design goal; if there are any situations which violate this constraint in such a way as to return incorrect results without signalling an error, the specification is in error, and must be corrected before being advanced. If there are such cases, then there needs to be some emergency repairs; if there are no such cases, the following is always safe, and will always use 1.1 when available: 1) clients which support HTTP/1.1 SHOULD send 1.1 requests 2) servers should echo the lesser of the request version and the supported protocol version. Otherwise, I call for a coin flip. Simon
Received on Tuesday, 31 December 1996 06:06:28 UTC