uNetworkingAB comments

Results 290 comments of


                                            uNetworkingAB

Strict Weak Ordering Check failing when adding an http handler

It is fixed now Den tis 3 dec. 2024 kl 22:23 skrev Brian Ferri ***@***.***>: > Encountering the same issue, is there going to be any ETA on a fix...

works with letsencrypt ?

Yes you need the fullchain file

Double-Free of UserData when gracefully closing a Websocket from Server-Side

Note to self: Could be WebSocket->end followed by WebSocket->close that doesn't work.

Double-Free of UserData when gracefully closing a Websocket from Server-Side

I don't remember the details but I think App.close will call WebSocket::close on all websockets. So the bug can probably be reproduced with any call to WebSocket::end followed immediately by...

Double-Free of UserData when gracefully closing a Websocket from Server-Side

You really don't mix end and close. Either you end, or you close. Not both. So it's probably missing a check in .close.

Double-Free of UserData when gracefully closing a Websocket from Server-Side

can you post a minimal reproducer in full

How to remove previously registered path in existing web-socket server.

If you pass nullptr instead of a handler it goes away

Method to indicate that request has body

hasBody is a good addition

Method to indicate that request has body

Obviously this should be hasBody() as we already do standards compliant check for this internally. So it's just setting a boolean and returning it via hasBody()

Method to indicate that request has body

bodyType() could return 0 for false, 1 for fix length, 2 for stream. The parser already knows all of this