There are several scenarios one need to pass more server options to underlying server factory:
Scenario 1: PFX certificates may be encrypted with password, so tls option passphrase should be supported.
Scenario 2: Some browser [see below] may require a HTTP/2 server configured to allow HTTP/1.1, so http2 option allowHTTP1 should be supported.
Scenario 3: When iOS Safari requesting a static page from local-web-server (firstrun when server started), it ocassionally causes 13% CPU utilization. maybe the server is not well configured.
So, just more server options!
continue from Scenario 2: ...
On Windows I use WSL Debian GNOME Web (Epiphany) to simulate desktop Safari. Latest stable Epiphany failed to connect to lws http2 server, the error is:
Unknown ALPN Protocol, expected h2 to be available.
If this is a HTTP request: The server was not configured with the allowHTTP1 option or a listener for the unknownProtocol event.
There are several scenarios one need to pass more server options to underlying server factory:
Scenario 1: PFX certificates may be encrypted with password, so tls option
passphrase
should be supported. Scenario 2: Some browser [see below] may require a HTTP/2 server configured to allow HTTP/1.1, so http2 optionallowHTTP1
should be supported. Scenario 3: When iOS Safari requesting a static page from local-web-server (firstrun when server started), it ocassionally causes 13% CPU utilization. maybe the server is not well configured.So, just more server options!
continue from Scenario 2: ...
On Windows I use WSL Debian GNOME Web (Epiphany) to simulate desktop Safari. Latest stable Epiphany failed to connect to lws http2 server, the error is: