Alex Sergeyev
Alex Sergeyev
Thanks for the report, I will get to it eventually or someone would PR before me, handling should not be too hard to add except in last case where error...
Let's start from basics. Websocketd can see following things from the client: - connect - disconnect Connect makes server start a program; disconnect makes server to do following: - close...
I don't see where in real life use this sort of situation would happen. Could you try to make example and demonstrate what happens where? if websocketd kills process it...
So far I think you're continuing theoretical discussion and I'm not seeing why it should be different in websocketd from what it's now. Special custom use (as a component that...
Ah.. good point on 1.0 - we probably need to define what LEVEL means in --loglevel=LEVEL and clarify things - make sure IPv6 works - I personally really want to...
Since we rolled out changes that were done in Server/Handler split we need to re-check how websocketd handles programs that ignore SIGTERM and/or take some time to terminate.
@Aginor404 why? They are concatenated eventually, I do not see benefit of splitting those.
Basic auth of some sort mentioned in #172
You kind of can ask your websocketd for stuff using curl: ``` curl -s -H "Connection: Upgrade" \ -H "Upgrade: websocket" \ -H "Host: localhost:8080" \ -H "Sec-WebSocket-Version: 13" \...
@meisterluk I like this idea. Not sure if it should be on different port or same, just with query string in URL... Say url?stderr=true&stdout=false would give you only stderr socket......