Return-Path: Delivered-To: apmail-new-httpd-archive@apache.org Received: (qmail 71855 invoked by uid 500); 15 May 2001 23:11:24 -0000 Mailing-List: contact new-httpd-help@apache.org; run by ezmlm Precedence: bulk Reply-To: new-httpd@apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list new-httpd@apache.org Received: (qmail 71506 invoked from network); 15 May 2001 23:11:17 -0000 Errors-To: Message-ID: <043101c0dd94$1bc49420$94c0b0d0@roweclan.net> From: "William A. Rowe, Jr." To: References: <016101c0dd44$16afaba0$bd431b09@sashimi> <009e01c0dd48$f79959a0$94c0b0d0@roweclan.net> <01bf01c0dd59$4a6fc280$bd431b09@sashimi> Subject: Re: Is this an Apache 1.3 bug or a config problem? Date: Tue, 15 May 2001 18:04:03 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N From: "Bill Stoddard" Sent: Tuesday, May 15, 2001 11:08 AM > So you are saying this is a bug for sure? It is east to update > r->server->port with what is in the local_addr->sin_port field right before > calling new_connection(). There is code in http_main.c that does just that > for some platforms. Not sure what the implications are though... * general/3787: SERVER_PORT is always 80 if client comes to any port => needs review by the protocol guys, I think.