You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@axis.apache.org by ax...@ws.apache.org on 2004/08/16 13:41:20 UTC

[jira] Closed: (AXISCPP-86) HTTP 1.1 chunking not supported

Message:

   The following issue has been closed.

   Resolver: Samisa Abeysinghe
       Date: Mon, 16 Aug 2004 4:41 AM

A patch was supplied by John and Adrian and was applied by Samisa.
With this patch, the client side Axis trasport can deal with HTTP 1.1 chunking.
---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/AXISCPP-86

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: AXISCPP-86
    Summary: HTTP 1.1 chunking not supported
       Type: Bug

     Status: Closed
   Priority: Major
 Resolution: FIXED

    Project: Axis-C++
 Components: 
             Transport (Server)
   Fix Fors:
             1.2 Final
   Versions:
             1.1 Final

   Assignee: Susantha Kumara
   Reporter: Sevwandi Abeysinghe

    Created: Thu, 6 May 2004 11:54 PM
    Updated: Mon, 16 Aug 2004 4:41 AM
Environment: All platforms

Description:
>From the discussion treads in the mailing lists, it is found out that there is a problem when you look for a way to have HTTP 1.1 chunked messages (and it is not so simple). Jean-Yves has first concentrated his efforts in the tooling so is the reason why the HTTP_1_0 macro has been added.

The code can only work for responses less than 1024 bytes. For 
HTTP 1.1 chunked message the client receiver should read messages by 
chunked size fragments. The deserialization process read messages by 
fragment of 1024 bytes (See operator >> in Channel.cpp). So the
implementation will failed for responses greater than 1024 bytes.

Another thing that is reported as confusing is the test for chunked in the code:

...
if(pos = strLine.find("Transfer Encoding: chunked"))
...

According to the discussion treads in the mailing lists this code will be evaluating as true in every case and WAS return "Transfer-Encoding" not "Transfer Encoding" and pos=-1 if the string is not found (so test is true).

The test cases that Jean-Yves has used with WAS can be found here:

  http://marc.theaimsgroup.com/?l=axis-c-dev&m=108151487330314&w=2

Just use AxisBench.wsdl to show the failure (server side only return the input parameter).




---------------------------------------------------------------------
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