[
https://issues.apache.org/jira/browse/AXIS2C-967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Lazarski resolved AXIS2C-967.
------------------------------------
Resolution: Won't Fix
Specific to old IIS behavior
> 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
> Priority: Major
>
> 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 was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
