So I' ve had some luck by adding a socket select call before trying to
read data from the socket in polarSSL . This seems to be the change that
made it work for me !

On Wed, Mar 2, 2011 at 1:35 PM, Daniel Stenberg <daniel_at_haxx.se> wrote:

> On Tue, 1 Mar 2011, Prashant R wrote:
>
> lwip should be oblivious to SSL per my understanding .
>>
>
> Sure, but it's not that hard to imagine that the SSL library uses the
> socket functions in a specific way that is quite different than what libcurl
> does when doing plain HTTP.
>
> I would recommend that you setup the simplest possible HTTPS server to work
> against, and then start debugging and communicate with the lwip team for
> some assistance and feedback.
>
> You could even build a matching libcurl + PolarSSL setup on a normala linux
> machine next to your target to see how a "normal" host works and acts when
> running against the same server on the same network.
>
> I'm afraid I don't see what we can do to help or how libcurl is actually to
> blame for any of this, or even how libcurl could be modified to make such
> debugging adventures easier...
>
> --
>
> / daniel.haxx.se
>
> -------------------------------------------------------------------
> List admin: http://cool.haxx.se/list/listinfo/curl-library
> Etiquette: http://curl.haxx.se/mail/etiquette.html
>

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