> I think the problem is more fundamental. If we force HTTP/1.0 clients > to accept HTTP/1.1 reponses, they also have to accept HTTP/1.2, > 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 -- Sameer Parekh Voice: 510-986-8770 President FAX: 510-986-8777 C2Net C2Net is having a party: http://www.c2.net/party/ http://www.c2.net/ sameer@c2.netReceived on Monday, 30 December 1996 13:24:36 UTC
This archive was generated by hypermail 2.4.0 : Thursday, 2 February 2023 18:43:00 UTC