Differences

This shows you the differences between two versions of the page.

--- litespeed_wiki:config:supported_quic_versions [2018/04/11 16:15]
Jackson Zhang [Supported versions should show automatically as far as QUIC versions set to blank]
+++ litespeed_wiki:config:supported_quic_versions [2018/05/04 14:34]
Lisa Clarke [Troubleshooting: Supported QUIC Versions Header is Wrong]
@@ Line 1: / Line 1: @@
-====== What Quic versions does LSWS support? ======
+====== What QUIC Versions Does LSWS Support? ======
-===== Supported versions should show automatically as far as "QUIC versions" set to blank =====
+===== Supported Versions Show Automatically =====
-Initially, LSWS supports Q035, Q037.  Now the latest version of LSWS supports Q035, Q037, Q038, Q039, but the supported versions should keep changing from both Chrome side and LSWS side. LSWS will automatically show the supported versions through the headers.
+Initially, LSWS supported Q035, Q037.  As of this writing, the latest version of LSWS supports Q035, Q037, Q038, Q039, but this will continue to change, as both Chrome and LiteSpeed Web Server evolve. LSWS will automatically show the supported QUIC versions through the headers.
-In LSWS QUIC setting "QUIC versions", you should not manually set any versions there and leave as Blank always.
+//Please do not change the LSWS **QUIC versions** setting!// Leave it as ''Not Set'', and the ''alt-svc'' response header will automatically display the currenly-supported versions.
 {{ :litespeed_wiki:config:quic-versions-setting-should-leave-blank.png?400 |}}
-then the header should show all latest supported version automatically:
 {{ :litespeed_wiki:config:quic-versions-correct-header.png?360 |}}
-===== Troubleshooting: Why my supported QUIC versions' header wrong? ====
+===== Troubleshooting: Supported QUIC Versions Header is Wrong ====
-Sometimes you can not see the latest supported version from QUIC header even LSWS's new release supports them. For example, at the time of this writing, LSWS supports Q035, Q037, Q038, Q039, but page header only show "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 |}}
 One possible reason is that you are using an old version of LSWS. You should always upgrade to the latest build of the latest version.
-If you have upgraded to the latest version so but still saw the above error, most likely you manually set "QUIC versions" in LSWS settings.
+If you have upgraded to the latest version but //still// see the above inaccuracy, the most likely explanation is that you manually set **QUIC Versions** in LSWS's QUIC settings.
 {{ :litespeed_wiki:config:quic-versions-wrong-setting.png?500 |}}
-You should already leave "QUIC versions" to blank, otherwise manual configuration will soon become outdated/wrong configuration.
+When **QUIC Versions** is not left as ''Not Set'', the manual configuration will soon become outdated or wrong.
-===== When to manually set "QUIC versions"? =====
+===== When to Manually Set "QUIC Versions" =====
-The idea behind exposing supported versions and having "QUIC versions" setting config is to give user ability to possibly disable some versions in case there is a security vulnerability or some bug. At and only at this occasion, you can set "QUIC versions" manually. However, you should remember to remove the setting to blank once the bug fixed to avoid outdated configuration problem in the future.
+Why have a **QUIC Versions** setting at all, if you are not supposed to use it?
+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.