Return-Path: Delivered-To: apmail-ws-axis-dev-archive@www.apache.org Received: (qmail 67913 invoked from network); 22 Mar 2004 03:18:36 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 22 Mar 2004 03:18:36 -0000 Received: (qmail 75083 invoked by uid 500); 22 Mar 2004 03:18:15 -0000 Delivered-To: apmail-ws-axis-dev-archive@ws.apache.org Received: (qmail 75063 invoked by uid 500); 22 Mar 2004 03:18:15 -0000 Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-dev@ws.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list axis-dev@ws.apache.org Received: (qmail 75052 invoked from network); 22 Mar 2004 03:18:14 -0000 Received: from unknown (HELO exchange.sun.com) (192.18.33.10) by daedalus.apache.org with SMTP; 22 Mar 2004 03:18:14 -0000 Received: (qmail 20128 invoked from network); 22 Mar 2004 03:18:58 -0000 Received: from localhost (HELO nagoya) (127.0.0.1) by nagoya.betaversion.org with SMTP; 22 Mar 2004 03:18:58 -0000 Message-ID: <171870112.1079925538111.JavaMail.apache@nagoya> Date: Sun, 21 Mar 2004 19:18:58 -0800 (PST) From: jira@apache.org To: axis-dev@ws.apache.org Subject: [jira] Commented: (AXIS-1251) Transfer-Encoding not prperly detected on a response stream Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N The following comment has been added to this issue: Author: Danno Ferrin Created: Sun, 21 Mar 2004 7:18 PM Body: Yes it is an axis bug. One should really do some homework before jumping up and shouting "Not our bug!" First, header field names and (for transfer-encoding) the value as well are case insensitive http://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.2 (first paragraph, third sentence) http://www.w3.org/Protocols/rfc2616/rfc2616-sec3.html#sec3.6 (third paragraph, first sentence) Second, Weblogic does send the field name in the mixed case way the spec defines it as (which is what the bug addresses), here's part of a TCP trace... HTTP/1.1 200 OK Date: Mon, 22 Mar 2004 03:07:38 GMT Server: WebLogic WebLogic Server 6.1 SP4 11/08/2002 21:50:43 #[snip] Content-Type: text/xml; charset=utf-8 Transfer-Encoding: Chunked Connection: Close 064d [snip] It's even a more obvious bug when you see the other headers in that same block that do have toLowerCase and the transfer-encoding one doesn't. --------------------------------------------------------------------- View this comment: http://issues.apache.org/jira/secure/ViewIssue.jspa?key=AXIS-1251&page=comments#action_26375 --------------------------------------------------------------------- View the issue: http://issues.apache.org/jira/secure/ViewIssue.jspa?key=AXIS-1251 Here is an overview of the issue: --------------------------------------------------------------------- Key: AXIS-1251 Summary: Transfer-Encoding not prperly detected on a response stream Type: Bug Status: Unassigned Priority: Major Project: Axis Versions: current (nightly) Assignee: Reporter: Danno Ferrin Created: Thu, 11 Mar 2004 2:07 PM Updated: Sun, 21 Mar 2004 7:18 PM Environment: Client and server are Windows XP SP1, J2SE 1.4.2_04. Server is Weblogic 6.1 SP4. Description: When using HTTP 1.1 transport and the server response with a chunked response I get some involved response about a lack of rocument element. The chunking markers are note being processed and being included in the HTTP response. This is because the header is palced in the cache as lower case but the key to fetch it is mixed case. Patch is attached --------------------------------------------------------------------- JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira