From 487915551d5f315e6dec0115c97e0ddf4278205d Mon Sep 17 00:00:00 2001 From: Lucas Clemente Date: Mon, 5 Jun 2017 15:17:15 +0200 Subject: [PATCH] Update quic-go logging instructions --- QUIC.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/QUIC.md b/QUIC.md index f673628..cdbf536 100644 --- a/QUIC.md +++ b/QUIC.md @@ -39,7 +39,7 @@ First, make sure your domain name is properly set in your Caddyfile and the comm 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, 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` or run Chrome with the host-resolver-rules option: `--host-resolver-rules='MAP foo.bar: 127.0.0.1:'` -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.) +If that's all good and you need more detailed output, launch caddy with the environment variable `QUIC_GO_LOG_LEVEL=2`. When you go to `chrome://net-internals/#events` you should see some QUIC events marked in red.