Re: [libmicrohttpd] upgrading and life cycle of sockets

[Christian Grothoff]

Hi Jose,

Well, technically you can dup() around this and call action close early.
HOWEVER, this breaks BADLY if you ever use TLS connections: here, MHD
will right now ensure that you write plaintext into your socket and turn
it into ciphertext for the network. That's why MHD needs to keep some
state per connection, and if you break that, well, kiss TLS-support goodbye.

So I would not recommend for applications to try to take any 'full
control' of the socket, simply because it may not be the real socket and
merely be a socketpair to talk to MHD's TLS-adapter ;-).

Happy hacking!

Christian

On 11/24/20 3:23 PM, José Bollo wrote:
> Hi there,
> 
> After a switching protocol for web socket for example, libmicrohttp
> keeps the socket under the table until a call to MHD_upgrade_action
> (something, MHD_UPGRADE_ACTION_CLOSE).
> 
> So, it enforces to have a link to libmicrohttp when using such switched
> protocol socket.
> 
> Is it possible to break that link? To tell libmicrohttp to forget and
> clean things related to that socket and let far part of code use the
> socket freely?
> 
> Best
> José
>

signature.asc
Description: OpenPGP digital signature