On Fri, Aug 19, 2011 at 8:50 AM, Daniel Stenberg <[email protected]> wrote:
> On Thu, 18 Aug 2011, amit paliwal wrote: > > 1) Use CONNECT_ONLY option to connect to the server >> 2) Once connection happens, I am manually constructing a HTTP GET and >> sending it to Server >> 3) Server is replying with HTTP 200 OK with subheader transfer-encoding: >> chunked >> 4) Disabling CONNECT_ONLY option >> > > Uhm, what's disabling that supposed to accomplish? Once you've taken > control of the socket with CONNECT_ONLY then the socket is yours and you can > not return it to libcurl in any particular sense except for closing the > entire easy handle with curl_easy_cleanup(). > > > 5) Receiving a chunk from Server, which has some meaning for my >> application >> 6) preparing HTTP POST and sending it to server by calling easy_perform(), >> immediate return type of this perform is "Timeout was reached" >> > > Are you doing that perform() on the same handle you did CONNECT_ONLY on? If > so, that just won't work and we could possibly work on detecting that better > to return a better error. > ------ In this case what will be the solution? I need to do initial step manually because of some requirements and then I want CURL to takeover and do HTTP POST send and HTTP OK receive for me. I wana connect to server and then I want Curl to send and receive HTTP on same socket. > > -- > > / daniel.haxx.se > ------------------------------**------------------------------**------- > List admin: > http://cool.haxx.se/list/**listinfo/curl-library<http://cool.haxx.se/list/listinfo/curl-library> > Etiquette: > http://curl.haxx.se/mail/**etiquette.html<http://curl.haxx.se/mail/etiquette.html> > -- Regards, Amit
------------------------------------------------------------------- List admin: http://cool.haxx.se/list/listinfo/curl-library Etiquette: http://curl.haxx.se/mail/etiquette.html
