comparison README @ 8547:57e5393e5d40 quic

QUIC: switched to draft 29 by default.
author Vladimir Homutov <vl@nginx.com>
date Fri, 11 Sep 2020 10:56:05 +0300
parents cec7f207a4bf
children dd8e50e11bfc
comparison
equal deleted inserted replaced
8546:eece8e35e64d 8547:57e5393e5d40
188 network.http.http3.enabled = true 188 network.http.http3.enabled = true
189 189
190 + to enable QUIC in Chrome, enable it on command line and force it 190 + to enable QUIC in Chrome, enable it on command line and force it
191 on your site: 191 on your site:
192 192
193 $ ./chrome --enable-quic --quic-version=h3-27 \ 193 $ ./chrome --enable-quic --quic-version=h3-29 \
194 --origin-to-force-quic-on=example.com:8443 194 --origin-to-force-quic-on=example.com:8443
195 195
196 * Console clients 196 * Console clients
197 197
198 Known to work: ngtcp2, firefox's neqo and chromium's console clients: 198 Known to work: ngtcp2, firefox's neqo and chromium's console clients:
200 $ examples/client 127.0.0.1 8443 https://example.com:8443/index.html 200 $ examples/client 127.0.0.1 8443 https://example.com:8443/index.html
201 201
202 $ ./neqo-client https://127.0.0.1:8443/ 202 $ ./neqo-client https://127.0.0.1:8443/
203 203
204 $ chromium-build/out/my_build/quic_client http://example.com:8443 \ 204 $ chromium-build/out/my_build/quic_client http://example.com:8443 \
205 --quic_version=h3-27 \ 205 --quic_version=h3-29 \
206 --allow_unknown_root_cert \ 206 --allow_unknown_root_cert \
207 --disable_certificate_verification 207 --disable_certificate_verification
208 208
209 209
210 If you've got it right, in the access log you should see something like: 210 If you've got it right, in the access log you should see something like:
211 211
212 127.0.0.1 - - [24/Apr/2020:11:27:29 +0300] "GET / HTTP/3" 200 805 "-" 212 127.0.0.1 - - [24/Apr/2020:11:27:29 +0300] "GET / HTTP/3" 200 805 "-"
213 "nghttp3/ngtcp2 client" "quic" "h3-27" 213 "nghttp3/ngtcp2 client" "quic" "h3-29"
214 214
215 215
216 5. Troubleshooting 216 5. Troubleshooting
217 217
218 Here are some tips that may help you to identify problems: 218 Here are some tips that may help you to identify problems:
219 219
220 + Ensure you are building with proper SSL library that 220 + Ensure you are building with proper SSL library that
221 implements draft 27 221 implements draft 29
222 222
223 + Ensure you are using the proper SSL library in runtime 223 + Ensure you are using the proper SSL library in runtime
224 (`nginx -V` will show you what you are using) 224 (`nginx -V` will show you what you are using)
225 225
226 + Ensure your client is actually sending QUIC requests 226 + Ensure your client is actually sending QUIC requests
249 If you are willing to contribute, please refer to 249 If you are willing to contribute, please refer to
250 http://nginx.org/en/docs/contributing_changes.html 250 http://nginx.org/en/docs/contributing_changes.html
251 251
252 7. Links 252 7. Links
253 253
254 [1] https://tools.ietf.org/html/draft-ietf-quic-transport-27 254 [1] https://tools.ietf.org/html/draft-ietf-quic-transport-29
255 [2] https://tools.ietf.org/html/draft-ietf-quic-http-27 255 [2] https://tools.ietf.org/html/draft-ietf-quic-http-29
256 [3] https://mailman.nginx.org/mailman/listinfo/nginx-devel 256 [3] https://mailman.nginx.org/mailman/listinfo/nginx-devel
257 [4] https://boringssl.googlesource.com/boringssl/ 257 [4] https://boringssl.googlesource.com/boringssl/
258 [5] https://tools.ietf.org/html/draft-ietf-quic-recovery-27 258 [5] https://tools.ietf.org/html/draft-ietf-quic-recovery-29
259 [6] https://nginx.org/en/docs/http/ngx_http_core_module.html#listen 259 [6] https://nginx.org/en/docs/http/ngx_http_core_module.html#listen
260 [7] https://nginx.org/en/docs/debugging_log.html 260 [7] https://nginx.org/en/docs/debugging_log.html