Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
litespeed_wiki:config:supported_quic_versions [2018/05/04 14:03] Lisa Clarke [Supported Versions Show Automatically] |
litespeed_wiki:config:supported_quic_versions [2018/05/04 14:34] Lisa Clarke [Troubleshooting: Supported QUIC Versions Header is Wrong] |
||
|---|---|---|---|
| Line 11: | Line 11: | ||
| ===== Troubleshooting: Supported QUIC Versions Header is Wrong ==== | ===== Troubleshooting: Supported QUIC Versions Header is Wrong ==== | ||
| - | Sometimes you cannot see the latest supported version from the QUIC header, even if LSWS's latest release supports them. For example, at the time of this writing, LSWS supports Q035, Q037, Q038, Q039, but the page header only shows ''35, 37''. Why? | + | Sometimes you cannot see the latest supported version from the QUIC header, even if LSWS's latest release supports them. For example, let's say, LSWS supports the fictional QUIC versions Q0XX, Q0YY, and Q0ZZ, but the page header only shows ''XX,YY''. Why? |
| {{ :litespeed_wiki:config:quic-versions-wrong-header.png?300 |}} | {{ :litespeed_wiki:config:quic-versions-wrong-header.png?300 |}} | ||
| Line 27: | Line 27: | ||
| The idea behind exposing supported versions is to give the user the ability to disable a particular QUIC version in the case of a security vulnerability or bug. //This is the only occasion during which you should set **QUIC Versions** manually//. | The idea behind exposing supported versions is to give the user the ability to disable a particular QUIC version in the case of a security vulnerability or bug. //This is the only occasion during which you should set **QUIC Versions** manually//. | ||
| - | Don't forget to revert the setting back to ''Not Set'' once the bug is fixed. Failure to do so will cause your configuration to become outdated in the future. | + | //Don't forget to revert the setting back to ''Not Set'' once the bug is fixed.// Failure to do so will cause your configuration to become outdated in the future. |