From 5512cb73868de0bddd1f1387df52458b3ad55bd1 Mon Sep 17 00:00:00 2001 From: twdkeule Date: Wed, 10 May 2017 14:53:32 +0200 Subject: [PATCH] Updated QUIC (markdown) --- QUIC.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/QUIC.md b/QUIC.md index dd4f35f..22b08a1 100644 --- a/QUIC.md +++ b/QUIC.md @@ -37,7 +37,7 @@ However the initial connection will still happen over TCP untill the first HTTP First, make sure your domain name is properly set in your Caddyfile and the command to launch Chrome _in all places_. Next, your site must use a trusted certificate as QUIC requires encryption. -You can create a CA yourself an add it to your CA-database. When using this self-signed certificate, it must contain a hostname with top-level domain, eg. `foo.bar`, for Chromium to correctly send a QUIC ClientHello message. For testing over localhost you can add an entry to /etc/hosts. +You can create a CA yourself an add it to your CA-database. When using this self-signed certificate, your site must have a hostname with top-level domain, eg. `foo.bar`, for Chromium to correctly send a QUIC ClientHello message. For testing over localhost you can add an entry to /etc/hosts. If that's all good and if you're even just a little bit savvy with Go, then you could add `import "github.com/lucas-clemente/quic-go/utils"` and call `utils.SetLogLevel(utils.LogLevelDebug)` somewhere in Caddy's main() function. That will provide very detailed output. (Note that this log utility is not meant to be a public API.)