[
https://issues.apache.org/jira/browse/AXIS2C-967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12869847#action_12869847
]
nadir amra commented on AXIS2C-967:
-----------------------------------
Just to add my experience with the HTTP transport from Axis C++, in a loop we
processed the HTTP 100 continue but stayed within the loop to read the next
HTTP header. As long as 100 continue was received we kept on reading from the
socket.
> libcurl interface assumes first response line is HTTP status, but it might be
> HTTP 100 Continue
> -----------------------------------------------------------------------------------------------
>
> Key: AXIS2C-967
> URL: https://issues.apache.org/jira/browse/AXIS2C-967
> Project: Axis2-C
> Issue Type: Bug
> Components: transport/http
> Environment: Windows XP, Visutal Studio 2005, libxml, libcurl
> Reporter: Bill Mitchell
>
> After receiving an HTTP response, the axis2_libcurl code assumes the first
> response line is the HTTP status line, and grabs the status code therein.
> While watching this communicate to an IIS server, I noticed that the first
> response was an HTTP 1.1/100 Continue, and the real status line was several
> lines later. I don't know if IIS sends the 100 Continue all of the time or
> just some of the time; regardless, it is allowed in the HTTP RFC 2616. The
> libcurl code needs to read through to find the first non-1xx HTTP status
> line, or process these headers in reverse order and grab the code from the
> last status line received.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
