Glenn Strauss

> Both lighttpd 1.4.74 and 1.4.75 compile fine after selecting the lighttpd-mod-mbedtls package. This makes CONFIG_LIGHTTPD_SSL_SELECT=m change automatically into CONFIG_LIGHTTPD_SSL_DEPENDS=y. So if this issue resolved for you? > Shouldn't menuconfig...

Sorry, I got side-tracked. Still fighting with Ubuntu and Debian to pretend like they know how to update software. I'll try to review this some time next week.

More detailed comment in #24004 regarding extending support to force the lighttpd base application to use openssl for crypto functions (such as SHA-256). @rodajc > Shouldn't menuconfig select lighttpd-mod-mbedtls automatically...

`server: lighttpd/1.4.58` Wow! That's old! lighttpd 1.4.58 was released Dec 2020, almost 3 1/2 years ago. Please test with the latest lighttpd release, lighttpd 1.4.76. Among other things, HAProxy can...

nori0428/mod_websocket is obsolete. lighttpd 1.4.46 and later support websockets and does not have the issue with case-sensitive headers reported above. https://redmine.lighttpd.net/projects/lighttpd/wiki/Docs_ModWStunnel provides a websocket tunnel through which client and a...

https://serverfault.com/questions/1114316/how-do-i-get-lighttpd-access-log-to-stdout

> Handling of Upgrade with a nonempty body is well-defined, but the Upgrade paths that are actually implemented today (WebSockets and MASQUE) only use GET requests with empty bodies. >...

Since we are discussing this publicly, I hope these details are appropriate. lighttpd 1.4.56 and later supports the HTTP/1.1 `Upgrade: h2c` (now deprecated by the RFCs), but lighttpd ignores `Upgrade:...

@kazuho > As I understand, this problem is specific to HTTP/1.1. Yes, the `Upgrade` request header is specific to HTTP/1.1. > In that respect, I like the idea of recommending...

@zohaib09 stop multiposting and instead read the documentation on lighttpd's website. nori0428/mod_websocket is obsolete. See https://github.com/nori0428/mod_websocket/issues/54