axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [jira] Commented: (AXIS-1251) Transfer-Encoding not prperly detected on a response stream
Date Mon, 22 Mar 2004 03:18:58 GMT
The following comment has been added to this issue:

     Author: Danno Ferrin
    Created: Sun, 21 Mar 2004 7:18 PM
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
(first paragraph, third sentence)
(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

<?xml version="1.0" encoding="utf-8"?>
<soapenv:Envelope xmlns:soapenv="" xmlns:xsd=""

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:

View the issue:

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
             current (nightly)

   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

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

This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:

If you want more information on JIRA, or have a bug to report see:

View raw message