Re: [PATCH] fixes relayd Websocket "Connection: close" header when Upgrade is requested

1.01.04 (Mon) 12:59 (CET): >> One month has passed, this is just a friendly ping... >> >> Marcus >> >> mcmer-open...@tor.at (Marcus MERIGHI), 2020.12.04 (Fri) 14:18 (CET): >>> This patch wasn't commited and not discussed (publicly). >>> >>>

Re: [PATCH] fixes relayd Websocket "Connection: close" header when Upgrade is requested

relayd as a front-end to the mattermost-server. > > Just a friendly reminder... > > @franz: Thank you! > > Marcus > > fr...@bett.ag (Franz Bettag), 2020.03.04 (Wed) 17:52 (CET): >> After migrating my home setup from nginx reverse proxying to relayd, i >> noticed my iOS devi

[PATCH] fixes relayd Websocket "Connection: close" header when Upgrade is requested

After migrating my home setup from nginx reverse proxying to relayd, i noticed my iOS devices having issues connecting through Websockets. After debugging, i noticed that relayd adds the "Connection: close" regardless of upgrade being requested. This issue is also reported on a blog-post using

[PATCH] make cwm parse /etc/ssh/ssh_known_hosts (global known hosts) as well as user's known_hosts

this. :) best regards Franz Bettag diff --git app/cwm/calmwm.h app/cwm/calmwm.h index 008c16e1..445dab9e 100644 --- app/cwm/calmwm.h +++ app/cwm/calmwm.h @@ -305,6 +305,7 @@ struct conf { int xrandr_event_base; char*conf_file; char