docker-nginx-http3 icon indicating copy to clipboard operation
docker-nginx-http3 copied to clipboard

Browser doesn't show h3 protocol

Open pako88 opened this issue 4 years ago • 10 comments
trafficstars

Hello,

i set up a website with this docker container as base image. everythings working fine so far. Except that somehow all browsers are still connecting with http2 (tested with latest chrome and latest firefox - http3 is enabled in all browsers - this was verified on https://quic.nginx.org/).
https://www.http3check.net/ and curl with forced http3 are showing that my website is correctly set up with http3. i also created a separate example with caddy and there the browsers are showing http3 correctly.

is this a known "issue" of this project?

Thanks

pako88 avatar May 31 '21 14:05 pako88

Same here, it is working when forced, but not in the Browser:

$ docker run -it --rm ymuski/curl-http3 curl -I --http3 https://xxxxx.xxx
HTTP/3 301
server: nginx
date: Sun, 06 Jun 2021 08:33:50 GMT
content-type: text/html; charset=UTF-8
vary: Accept-Encoding
x-powered-by: PHP/7.4.19
alt-svc: ma=86400,h3=":443"; ma=86400,quic=":443"

der--flo avatar Jun 06 '21 08:06 der--flo

@pako88 @der--flo Please try with latest image.

distributedlock avatar Jun 10 '21 01:06 distributedlock

No luck for me.

btw. your readme tells "Alpine Linux image with nginx 1.19.5 (mainline) ", but in the Dockerfile you use "ENV NGINX_VERSION 1.16.1"

built it with

ENV NGINX_VERSION 1.19.5
ENV QUICHE_COMMIT 6d070ed8694216806f3ce689d71ceb7ad76d425e

now it works with Firefox 89 and Chrome 90.0.4430.212

der--flo avatar Jun 10 '21 05:06 der--flo

@der--flo the quiche H3 doesn't work with nginx 1.19.5. I have moved nginx to the latest supported version which is 1.16.1. H3 should be working now and I see your latest edit now saying it is working for you.

distributedlock avatar Jun 12 '21 15:06 distributedlock

still no luck for me. Latest version in repository and changes from @der--flo are both not working for me

pako88 avatar Jun 26 '21 08:06 pako88

Please try again with this header in 8ef7b85597ca3b2d2127352c746c3fe041450185.

distributedlock avatar Jul 22 '21 17:07 distributedlock

I have exactly same problem. It works well with cURL, but not with browsers... So, any solution?

vadymmasiuk avatar Aug 19 '21 14:08 vadymmasiuk

With 8ef7b85597ca3b2d2127352c746c3fe041450185 applied in your nginx conf it is still failing?

distributedlock avatar Aug 21 '21 05:08 distributedlock

With 8ef7b85 applied in your nginx conf it is still failing?

Yes Anyway I have changed little bit to get it working: add_header alt-svc 'h3=":443"; ma=600,h3-29=":443"; ma=600,h2=":443"; ma=600,quic=":443"; ma=600; v="46,43"';

seems like h3-27 and 28 are not supported anymore with latest Chromium-based releases

vadymmasiuk avatar Aug 21 '21 14:08 vadymmasiuk

With 8ef7b85 applied in your nginx conf it is still failing?

Yes Anyway I have changed little bit to get it working: add_header alt-svc 'h3=":443"; ma=600,h3-29=":443"; ma=600,h2=":443"; ma=600,quic=":443"; ma=600; v="46,43"';

seems like h3-27 and 28 are not supported anymore with latest Chromium-based releases

Didn't help 💁🏻

steklopod avatar Dec 12 '21 13:12 steklopod