Differences

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

--- litespeed_wiki:config:enable_quic [2019/01/09 20:13]
Jackson Zhang
+++ litespeed_wiki:config:enable_quic [2019/01/24 17:55]
qtwrk [How to Open UDP Port 433 at the Firewall]
@@ Line 11: / Line 11: @@
-===== How to Open UDP Port 433 at the Firewall =====
+===== How to Open UDP Port 443 at the Firewall =====
 [[https://en.wikipedia.org/wiki/QUIC|QUIC]] runs a stream-multiplexing protocol over Transport Layer Security (TLS) on top of UDP instead of TCP. Be sure you've enabled the port with both TCP //and// UDP. Most of the time, TCP 443 is enabled.
@@ Line 88: / Line 88: @@
 Please keep in mind that CloudFlare doesn't support QUIC yet at the time of this writing. If you are behind CloudFlare, please disable it before testing/using QUIC.
-==== Possibly Google Chrome not enabling QUIC by default ====
+==== Possibly Google Chrome has not enabled QUIC by default ====
-At some period as we can see, Google Chrome decided to temporarily disable QUIC in browser and people explicitly have to go enable QUIC under ''chrome://flags''. You may not be necessary this case, however it might be good to check and ensure QUIC is enabled in Chrome.
+At some point we noticed that Google Chrome decided to temporarily disable QUIC by default. Some users explicitly have to enable QUIC under ''<nowiki>chrome://flags</nowiki>''. This may not be the case for you, but it's a good idea to check whether QUIC is enabled in Chrome.
+==== Possibly bad cached SSL certificates ====
+Sometimes, especially when the site in question has encountered an SSL/TLS error before, Chrome will save the certificate in cache and cause QUIC to be unable to establish a connection. In this case, it can simply be fixed by clearing the browser cache.