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:enable_quic [2019/01/09 21:05] Lisa Clarke [Possibly Google Chrome has not enabled QUIC by default] |
litespeed_wiki:config:enable_quic [2019/01/15 14:42] qtwrk [Possibly bad cached SSL certificates] |
||
|---|---|---|---|
| Line 90: | Line 90: | ||
| ==== Possibly Google Chrome has not enabled QUIC by default ==== | ==== Possibly Google Chrome has not enabled QUIC by default ==== | ||
| 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. | 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, specially when the site in question encountered a SSL/TLS error before, Chrome will save the certificate in cache and cause QUIC unable to establish connection, in this case it can simply fixed by clean browser cache. | ||