Cutlery/caddy
1
0
Fork 0
mirror of https://github.com/caddyserver/caddy.git synced 2025-07-09 03:04:57 -04:00
Code Issues Actions Packages Projects Releases Wiki Activity

Update quic-go logging instructions

Lucas Clemente 2017-06-05 15:17:15 +02:00
parent 1fa6c119ec
commit 487915551d
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
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:<port> 127.0.0.1:<local_port>'`
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.