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 ji...@apache.org on 2004/05/24 15:10:01 UTC

[jira] Commented: (AXISCPP-92) SOAP client does not support chuncked transfer encoding

The following comment has been added to this issue:

     Author: James Guido
    Created: Mon, 24 May 2004 6:09 AM
       Body:
I attached the fix (AxisTransport.cpp, HttpTransport.cpp and HttpTransport.hpp) I implemented to support "chunked" transfer encoding. The fix involves using cURL as the client's HTTP transport layer. cURL can be found at http://curl.haxx.se/. cURL gives a fairly easy API for performing HTTP and HTTPS. Definitely worth consideration. The fix eliminated the Channel, Sender and Receiver classes. I have tested for HTTP and it is working. I have no tested HTTPS.
---------------------------------------------------------------------
View this comment:
  http://issues.apache.org/jira/browse/AXISCPP-92?page=comments#action_35696

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/AXISCPP-92

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: AXISCPP-92
    Summary: SOAP client does not support chuncked transfer encoding
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Axis-C++
 Components: 
             Transport (Client)
   Versions:
             unspecified

   Assignee: 
   Reporter: James Guido

    Created: Mon, 24 May 2004 5:46 AM
    Updated: Mon, 24 May 2004 6:09 AM
Environment: HP-UX 11.0 with gnu compiler (Axis C++ v. 1.1.1, May 7)

Description:
Function GetPayLoad in HttpTransport class skips the whole SOAP message, because it searches for "Content-Length" HTTP header which is not available when using "chuncked" transfer-encoding.


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