[Libwebsockets] http client: seeing delayed SSL connection

Joel Winarske joel.winarske at gmail.com
Wed Feb 22 02:16:36 CET 2017

Well I'm calling it a delay, but I suspect it's just the expected behavior
of the "service loop".  Given http client is not a single synchronous
function call.

The scenario is loading the "site".  Which is around 275 server requests on
initial load.  Of which only the second occurring Method: POST '/rest/send'
is "refused"/or "pending".  I never see the incoming request in the log.
Chrome doesn't always report the transaction "refused".  Most of the time
it says "pending", which in Wireshark - the server doesn't respond.  So the
pattern is every other POST '/rest/send', of which calls the http client

On Tue, Feb 21, 2017 at 3:00 PM, Andy Green <andy at warmcat.com> wrote:

> On February 22, 2017 7:46:12 AM GMT+09:00, Joel Winarske <
> joel.winarske at gmail.com> wrote:
> >lwsws on Windows, so libuv.
> Right.
> >Timing wise the refused request happens during
> >lws_ssl_client_connect2().
> If we believe it really is a "connection refused" specifically, and not
> something else that falls into the general category of "my connection was
> not accepted", it's more interesting to understand the state of the server
> part at that time.  We are spamming it with connections?  Something else?
> >Also how do I get rid of the delay between lws_client_connect_via_info
> >and
> >lws_ssl_client_connect2()?
> ... what delay?
> -Andy
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://libwebsockets.org/pipermail/libwebsockets/attachments/20170221/5cb06b8e/attachment-0002.html>

More information about the Libwebsockets mailing list