mirror of
https://github.com/caddyserver/caddy.git
synced 2025-07-09 03:04:57 -04:00
Update command to run Chrome with whitelist parameter
parent
f863d58fa7
commit
c59470ba71
7
QUIC.md
7
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"
|
||||
```
|
||||
|
||||
|
||||
|
Loading…
x
Reference in New Issue
Block a user