[Libwebsockets] [EXTERNAL] Re: how to use LWSMPRO_CALLBACK
awilk at kramerav.com
Sun Jun 27 09:53:40 CEST 2021
The problem was that I used curl for the multipart post request, and the curl was using the wrong libssl.
Once I updated curl the problem was fixed.
From: Avigail Wilk
Sent: Tuesday, June 22, 2021 11:09 AM
To: Andy Green <andy at warmcat.com>; libwebsockets at ml.libwebsockets.org
Subject: RE: [EXTERNAL] Re: how to use LWSMPRO_CALLBACK
Thanks for your quick response.
I changed the name of http protocol but still have the same behavior.
I traced the two different ways -
When I use LWSMPRO_CALLBACK:
When I use LWSMPRO_FILE:
I am attaching a full trace of both mounts.
Let me add, that I upgraded libwebsockets from v2.0 to v4.2.0, and in v2.0 all requests worked as expected.
Thanks again for your support!
From: Andy Green <andy at warmcat.com>
Sent: Monday, June 21, 2021 3:05 PM
To: Avigail Wilk <awilk at kramerav.com>; libwebsockets at ml.libwebsockets.org
Subject: [EXTERNAL] Re: how to use LWSMPRO_CALLBACK
On 6/21/21 12:07 PM, Avigail Wilk wrote:
> I am using libwebsockets v4.2.0.
> I want to serve all the HTTP requests through my own callback, so
> therefor I used LWSMPRO_CALLBACK in the mounts:
> Where "http-only" is the name of http protocol.
> And the multi-part posted completed as expected.
> Do you have any idea of what I am doing wrong?
Missing callbacks while everything proceeds can be to do with binding to the wrong protocol... lws itself has a built-in protocol "http-only"
maybe try a different name
if that's not it maybe you can trace what lws does the two different ways.
CAUTION:This email originated from outside of the organization.
Do not click links or open attachments unless you recognize the sender and know the content is safe.
This message has been scanned for malware by Websense. www.websense.com
More information about the Libwebsockets