From c59470ba7152a3eb2e90ac36425408188fe3ceb9 Mon Sep 17 00:00:00 2001 From: Matt Holt Date: Mon, 20 Jun 2016 13:52:33 -0600 Subject: [PATCH] Update command to run Chrome with whitelist parameter --- QUIC.md | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/QUIC.md b/QUIC.md index fd9f076..5e6fb87 100644 --- a/QUIC.md +++ b/QUIC.md @@ -6,17 +6,16 @@ $ caddy -quic **(Note: Caddy 0.9 is [in beta](https://forum.caddyserver.com/t/caddy-0-9-beta-version-available/146))** -Sites that you serve with TLS will be shuttled over the wire by QUIC. +Sites that you serve with TLS will be shuttled over the wire by QUIC if the client supports it. -As for the client-side, you will probably have to run Chrome with special parameters. On a Mac (replace YOUR_SITE with your site's hostname): +To try it, you'll need to run Chrome with special parameters until they remove the whitelist limitations. On a Mac (replace both occurrences of YOUR_SITE with your site's hostname): ``` $ /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome \ --user-data-dir=/tmp/chrome \ --no-proxy-server \ --enable-quic \ - --origin-to-force-quic-on=YOUR_SITE:443 \ - --host-resolver-rules='MAP YOUR_SITE:443 127.0.0.1:443' 'https://YOUR_SITE/' + --quic-host-whitelist="YOUR_SITE" "YOUR_SITE" ```