Return-Path: Delivered-To: apmail-jakarta-tomcat-dev-archive@apache.org Received: (qmail 56087 invoked from network); 11 Apr 2002 10:11:31 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 11 Apr 2002 10:11:31 -0000 Received: (qmail 13178 invoked by uid 97); 11 Apr 2002 10:11:39 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-dev@jakarta.apache.org Received: (qmail 13162 invoked by uid 97); 11 Apr 2002 10:11:39 -0000 Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Developers List" Reply-To: "Tomcat Developers List" Delivered-To: mailing list tomcat-dev@jakarta.apache.org Received: (qmail 13144 invoked from network); 11 Apr 2002 10:11:38 -0000 Message-ID: <01a201c1e141$4fb154b0$27080b50@apache.org> From: "Remy Maucherat" To: "Tomcat Developers List" References: <80F5674514B4D311BAFC0040F6A45EEE2650B6@ntserver> Subject: Re: cvs commit: jakarta-tomcat-connectors/http11/src/java/org/apache/coyote/http11 Http11Processor.java Date: Thu, 11 Apr 2002 03:11:55 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Spam-Rating: localhost.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N > > De: Remy Maucherat [mailto:remm@apache.org] > > Enviado el: jueves 11 de abril de 2002 10:57 > > > > -- Degrade to the socket port on HTTP/1.0 requests with a > > Host header > > but no port number. > > > > > if you are under a nat, dafaulting to the socket port maybe no correct, > you could have tomcat in 8080, and the request would be redirected from > a 80 port, so if a host header with no port is present the correct > behavior should be to degrade to 80, without taking the socket port into > consideration, as the client can actually see it as 80.. so we must obey > the host header ever if present.. That's what is done. In HTTP/1.0, there's no host header defined in the spec, so a client using and expecting it to work is non-compliant. In HTTP/1.1, we always follow the host header, and ignore what the socket says, according to the spec. Remy -- To unsubscribe, e-mail: For additional commands, e-mail: