Received: by taz.hyperreal.com (8.7.5/V2.0) id SAA14284; Sun, 1 Sep 1996 18:29:39 -0700 (PDT) Received: from localhost by taz.hyperreal.com (8.7.5/V2.0) with SMTP id SAA14275; Sun, 1 Sep 1996 18:29:35 -0700 (PDT) X-Received: from paris.ics.uci.edu by taz.hyperreal.com (8.7.5/V2.0) with SMTP id OAA07366; Sat, 31 Aug 1996 14:54:23 -0700 (PDT) X-Received: from liege.ics.uci.edu by paris.ics.uci.edu id aa06158; 31 Aug 96 14:52 PDT To: new-httpd@hyperreal.com Subject: Re: HTTP/1.1 In-reply-to: Your message of "Fri, 30 Aug 1996 23:06:14 PDT." Date: Sat, 31 Aug 1996 14:52:19 -0700 From: "Roy T. Fielding" Message-ID: <9608311452.aa06158@paris.ics.uci.edu> ReSent-Date: Sun, 1 Sep 1996 18:29:31 -0700 (PDT) ReSent-From: Brian Behlendorf ReSent-To: new-httpd@hyperreal.com ReSent-Message-ID: Sender: owner-new-httpd@apache.org Precedence: bulk Reply-To: new-httpd@hyperreal.com > The IESG has approved HTTP/1.1 as a proposed standard. Whee. So, I'd > like to commit the following patch. It basically just turns on the > HTTP/1.1 label and cleans up persistent connection support a bit. +1, BUT is there any way to switch the protocol back to HTTP/1.0 if mod_proxy is in use? I would prefer not to enable 1.1+proxy until mod_proxy is at least conditionally compliant. [of course, this will be a moot point if someone upgrades mod_proxy this weekend] .....Roy