mirror/nginx
1
0
Fork 0
mirror of https://github.com/nginx/nginx.git synced 2025-06-20 20:51:09 +08:00
Code Issues Actions Packages Projects Releases Wiki Activity

README: updated to QUICv1.

Browse Source 
While here, removed old browsers tips.
This commit is contained in:
Sergey Kandaurov 2022-01-26 14:15:40 +03:00
parent c242f9f88e
commit fdc6ab8319
1 changed files with 4 additions and 17 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

21
README
View File

@ -34,8 +34,7 @@ Experimental QUIC support for nginx
What works now: What works now:
Currently we support IETF-QUIC draft-29 through final RFC documents. We support IETF QUIC version 1. Internet drafts are no longer supported.
Earlier drafts are NOT supported as they have incompatible wire format.
nginx should be able to respond to HTTP/3 requests over QUIC and nginx should be able to respond to HTTP/3 requests over QUIC and
it should be possible to upload and download big files without errors. it should be possible to upload and download big files without errors.
@ -178,21 +177,12 @@ Example configuration:
* Browsers * Browsers
Known to work: Firefox 80+ and Chrome 85+ (QUIC draft 29+) Known to work: Firefox 90+ and Chrome 92+ (QUIC version 1)
Beware of strange issues: sometimes browser may decide to ignore QUIC Beware of strange issues: sometimes browser may decide to ignore QUIC
Cache clearing/restart might help. Always check access.log and Cache clearing/restart might help. Always check access.log and
error.log to make sure you are using HTTP/3 and not TCP https. error.log to make sure you are using HTTP/3 and not TCP https.
+ to enable QUIC in Firefox, set the following in 'about:config':
network.http.http3.enabled = true
+ to enable QUIC in Chrome, enable it on command line and force it
on your site:
$ ./chrome --enable-quic --quic-version=h3-29 \
--origin-to-force-quic-on=example.com:8443
* Console clients * Console clients
Known to work: ngtcp2, firefox's neqo and chromium's console clients: Known to work: ngtcp2, firefox's neqo and chromium's console clients:
@ -201,10 +191,7 @@ Example configuration:
$ ./neqo-client https://127.0.0.1:8443/ $ ./neqo-client https://127.0.0.1:8443/
$ chromium-build/out/my_build/quic_client http://example.com:8443 \ $ chromium-build/out/my_build/quic_client http://example.com:8443
--quic_version=h3-29 \
--allow_unknown_root_cert \
--disable_certificate_verification
If you've got it right, in the access log you should see something like: If you've got it right, in the access log you should see something like:
@ -222,7 +209,7 @@ Example configuration:
+ Ensure you are using the proper SSL library in runtime + Ensure you are using the proper SSL library in runtime
(`nginx -V` will show you what you are using) (`nginx -V` will show you what you are using)
+ Ensure your client is actually sending QUIC requests + Ensure your client is actually sending requests over QUIC
(see "Clients" section about browsers and cache) (see "Clients" section about browsers and cache)
We recommend to start with simple console client like ngtcp2 We recommend to start with simple console client like ngtcp2