Return-Path: Delivered-To: apmail-tomcat-dev-archive@www.apache.org Received: (qmail 79277 invoked from network); 5 Mar 2008 17:38:29 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 5 Mar 2008 17:38:29 -0000 Received: (qmail 90455 invoked by uid 500); 5 Mar 2008 17:38:18 -0000 Delivered-To: apmail-tomcat-dev-archive@tomcat.apache.org Received: (qmail 90406 invoked by uid 500); 5 Mar 2008 17:38:18 -0000 Mailing-List: contact dev-help@tomcat.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Tomcat Developers List" Delivered-To: mailing list dev@tomcat.apache.org Received: (qmail 90395 invoked by uid 99); 5 Mar 2008 17:38:17 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 05 Mar 2008 09:38:17 -0800 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [64.202.165.182] (HELO smtpauth02.prod.mesa1.secureserver.net) (64.202.165.182) by apache.org (qpsmtpd/0.29) with SMTP; Wed, 05 Mar 2008 17:37:30 +0000 Received: (qmail 10722 invoked from network); 5 Mar 2008 17:37:48 -0000 Received: from unknown (67.162.45.134) by smtpauth02.prod.mesa1.secureserver.net (64.202.165.182) with ESMTP; 05 Mar 2008 17:37:48 -0000 Message-ID: <47CEDA68.2080802@rowe-clan.net> Date: Wed, 05 Mar 2008 11:37:44 -0600 From: "William A. Rowe, Jr." User-Agent: Thunderbird 2.0.0.12 (X11/20080226) MIME-Version: 1.0 To: Tomcat Developers List Subject: Re: Reorder the http header generated by tomcat References: <5D2BB7E5-6485-43DD-9DB3-9EEF3FB6648C@jaguNET.com> <47CEC51D.9070706@mhsoftware.com> <1632237F-F4DF-4A01-B6B3-01EE0E42ACCC@jaguNET.com> In-Reply-To: <1632237F-F4DF-4A01-B6B3-01EE0E42ACCC@jaguNET.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Jim Jagielski wrote: > Requiring any specific order on HTTP response headers is > completely bogus... :) To elaborate on why Jim thinks so (and we all agree)... - it's not spec. You cannot rely on this when authoring a user agent. - proxies can and will reorder whatever pretty order you assign to the response headers from the server agent. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org For additional commands, e-mail: dev-help@tomcat.apache.org