[Libwebsockets] [EXTERNAL] Re: mounts entry in lws_context_creation_info structure for HTTP MULTIPART POST
awilk at kramerav.com
Tue May 25 12:38:38 CEST 2021
Thanks a lot! I really appreciate your quick support and useful guidance.
I will take a look at the links you sent.
From: andy at warmcat.com <andy at warmcat.com>
Sent: Tuesday, May 25, 2021 11:33 AM
To: Avigail Wilk <awilk at kramerav.com>; libwebsockets at ml.libwebsockets.org
Subject: RE: [EXTERNAL] Re: [Libwebsockets] mounts entry in lws_context_creation_info structure for HTTP MULTIPART POST
On May 25, 2021 8:21:55 AM UTC, Avigail Wilk <awilk at kramerav.com> wrote:
>1. our need is to implement a REST API, for every HTTP request
>GET/POST/PUT we would like to trigger the Application differently and
>build a response differently based on the URI.
So you can handle this in the protocol callback... POST needs handling differently but the examples should show the way, eg
>2. We have the need to play with HEADERS and change HTTP headers for
>every HTTP response (from a security aspect), how can we inject this ?
Look through the examples.
>3. We need to maintain Basic HTTP authentication mechanism working
>based on private data and not based on an external file.
>From: Andy Green <andy at warmcat.com>
>Sent: Tuesday, May 25, 2021 10:45 AM
>To: Avigail Wilk <awilk at kramerav.com>;
>libwebsockets at ml.libwebsockets.org
>Subject: [EXTERNAL] Re: [Libwebsockets] mounts entry in
>lws_context_creation_info structure for HTTP MULTIPART POST
>On 5/24/21 4:06 PM, Avigail Wilk wrote:
>> I am using libwebsocket version 4.2.0.
>> I ran the server and the client and all worked as expected, except
>> HTTP MULTIPART POST.
>> Once I initiated the 'mount' entry as following, the HTTP MULTIPART
>> POST worked too:
>> Is the only way serving HTTP MULTIPART POST by using mounts?
>Apparently... what's the problem with defining a mount like that and
>getting on with your life?
>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