ankit Tripathi wrote:

> Actually this is the test application.in my application i have to wait
until
> some request comes from the PEER.we can't use curl_easy_recv() untill
the
> socket is not ready so here i am waiting on the select.

If the test is wrong, test results are erroneous too !!!

The server never requests anything to the client with the http(s)
protocol. The CLIENT performs the requests. See
http://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_message

> Did you mean that i should send some message to PEER before going to
> sleep on socket for receiving the msg from PEER.i also tried that
thing .
> while setting the CURL_CONNECT_ONLY msg we don't allow any header to
go
> to PEER.so manually i sent the header request " "GET /
HTTP/1.0\r\nHost:
> google.com:443\r\n\r\n" to the PEER .but that trick also din not
work.

Should have worked: I mean if sent properly, it should have caused the
server to reply. However I'm convinced your select call does not catch
inputs from server.

CURLOPT_CONNECT_ONLY allows you to open a socket without handling the
underlying protocol: as a consequence, you have to do it yourself...

I'm afraid your problem is not directly related to libcurl, since you do
not use one of the internal protocol handlers. But https is fully
supported by libcurl, thus I suggest you use it with the appropriate
callbacks (and CURLOPT_CONNECT_ONLY = 0) or else get some help around
you with direct programming of the http protocol.

Patrick

-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http://curl.haxx.se/mail/etiquette.html
Received on 2012-03-06