axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Senaka Fernando (JIRA)" <>
Subject [jira] Commented: (AXIS2C-967) libcurl interface assumes first response line is HTTP status, but it might be HTTP 100 Continue
Date Wed, 06 Feb 2008 09:57:08 GMT


Senaka Fernando commented on AXIS2C-967:

Hi Bill,

No it is correct to read the first line. Even a 100 continue is a valid HTTP status, [1].
We must process that and then consider any trailing responses. Processing may be checking
whether the client has nothing more to send. We can perhaps log a message. What if the server
expects the client to send more? Thus, it is not done to simply ignore it. I think it is better
if we could have a discussion on this on the dev-list. My concern is with RESTful invocations
mainly, where we'd be considering many status codes unlike SOAP that considers 200, 202, and

Answering your reverse seek situation. I believe the server requires us to understand a response
in order, and we must understand statuses one-by-one and if we can't recognize a status we
must report an error and exit, without making any assumptions.

Also, I believe that this is not a bug in our implementation. Rather, we need an improvement
to understand 100 continue responses.



> libcurl interface assumes first response line is HTTP status, but it might be HTTP 100
> -----------------------------------------------------------------------------------------------
>                 Key: AXIS2C-967
>                 URL:
>             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:
For additional commands, e-mail:

View raw message