On Thu, 13 Dec 2007, Jean Marie COUPRIE wrote:

> Please add in the Man page of Curl (in big characters) a warning saying that
> if the application send several messages to answer 1 Curl request, Curl see
> (and give to the user) only the first one that may be very different from
> what a browser see.

I don't see how that makes any sense. curl fetches the response from the
server. A single request gets a single response. I think you're confusing
matters, but I can't exactly figure out how.

Can you please elaborate?

> Is it possible to give to the user all the messages received before a
> time-out with separators between them ?

I believe you're talking about HTTP here? HTTP 1.1 works as defined by
RFC2616, and curl does its best to adhere to that. Can you please point out
what parts you claim it fails to follow?

> An other problem that I have found, but it may be particular to the Rexx
> port that I use, Curl keep the information that it has to post and post in
> the requests following the normal post request.

Now you're talking libcurl here, right? An easy handle in libcurl keeps all
the set options until you change them. That means that if you set data to
POST, that data will be sent with the handle on all future requests done with
that handle unless you change the option in between the requests. This is
documented and should not be a suprise.

Or did I misunderstand?

(and libcurl stuff is better taken to the curl-library mailing list...)

> I had to reset the post option. Is this a bug to report to the author of the
> Rexx port ?

The Rexx binding most probably works like that since libcurl itself works like
that.

-- 
  Commercial curl and libcurl Technical Support: http://haxx.se/curl.html