HTTP/3 doesn't work when used both for socket-activated sockets and sockets created on the custom network

[eriksjolund]

I had some success with setting up HTTP/3.

Design goal:
The traefik container serves HTTP/3 on the socket-activated sockets.
The traefik container also creates listening sockets on the custom network mynet and serves HTTP/3.

I didn't succeed getting that to work. If anyone knows how to accomplish the above goal, please let me know.

But I managed to get something working:

http3-inside

One configuration variant that I named http3-inside supports this:

HTTP/3 is available on the custom network mynet.
HTTP2 is available on the socket-activated sockets.

http3-outside

One configuration variant that I named http3-outside supports this:

HTTP/3 is available on the socket-activated sockets.

Show curl output

result of curl commands:

click me for details

commands:

bash install.bash $imagedir $variant

bash ./${variant}/run.bash

output when using variant=http3-inside

_________ test HTTP/3 _________
1. connect from inside the custom network and use HTTP/3
Hostname: a4840a9ff48a
IP: 127.0.0.1
IP: ::1
IP: 10.89.0.2
IP: fe80::5430:f7ff:fec6:2837
RemoteAddr: 10.89.0.3:46660
GET / HTTP/1.1
Host: whoami
User-Agent: curl/8.13.0
Accept: */*
Accept-Encoding: gzip
X-Forwarded-For: 10.89.0.9
X-Forwarded-Host: whoami.example.com
X-Forwarded-Port: 443
X-Forwarded-Proto: https
X-Forwarded-Server: e8a790c213a4
X-Real-Ip: 10.89.0.9


2. connect from outside the custom network to the socket-activated sockets and use HTTP/3

_________ test HTTP2 __________
3. connect from inside the custom network and use HTTP2
Hostname: a4840a9ff48a
IP: 127.0.0.1
IP: ::1
IP: 10.89.0.2
IP: fe80::5430:f7ff:fec6:2837
RemoteAddr: 10.89.0.3:46660
GET / HTTP/1.1
Host: whoami
User-Agent: curl/8.13.0
Accept: */*
Accept-Encoding: gzip
X-Forwarded-For: 10.89.0.10
X-Forwarded-Host: whoami.example.com
X-Forwarded-Port: 443
X-Forwarded-Proto: https
X-Forwarded-Server: e8a790c213a4
X-Real-Ip: 10.89.0.10


4. connect from inside the custom network to the socket-activated sockets and use HTTP2
Hostname: a4840a9ff48a
IP: 127.0.0.1
IP: ::1
IP: 10.89.0.2
IP: fe80::5430:f7ff:fec6:2837
RemoteAddr: 10.89.0.3:46660
GET / HTTP/1.1
Host: whoami
User-Agent: curl/8.13.0
Accept: */*
Accept-Encoding: gzip
X-Forwarded-For: 10.0.2.15
X-Forwarded-Host: whoami.example.com
X-Forwarded-Port: 443
X-Forwarded-Proto: https
X-Forwarded-Server: e8a790c213a4
X-Real-Ip: 10.0.2.15


_________ test HTTP ___________
5. connect from inside the custom network and use HTTP
* Host whoami.example.com:80 was resolved.
* IPv6: (none)
* IPv4: 10.89.0.3
Moved Permanently*   Trying 10.89.0.3:80...
* Connected to whoami.example.com (10.89.0.3) port 80
* using HTTP/1.x
> GET / HTTP/1.1
> Host: whoami.example.com
> User-Agent: curl/8.13.0
> Accept: */*
> 
* Request completely sent off
< HTTP/1.1 301 Moved Permanently
< Location: https://whoami.example.com/
< Date: Sun, 25 May 2025 10:39:39 GMT
< Content-Length: 17
< 
{ [17 bytes data]
* Connection #0 to host whoami.example.com left intact

6. connect from outside the custom network to the socket-activated sockets and use HTTP
* Host whoami.example.com:80 was resolved.
* IPv6: (none)
* IPv4: 169.254.1.2
*   Trying 169.254.1.2:80...
* Connected to whoami.example.com (169.254.1.2) port 80
* using HTTP/1.x
> GET / HTTP/1.1
> Host: whoami.example.com
> User-Agent: curl/8.13.0
> Accept: */*
> 
* Request completely sent off
< HTTP/1.1 301 Moved Permanently
< Location: https://whoami.example.com/
< Date: Sun, 25 May 2025 10:39:39 GMT
< Content-Length: 17
< 
{ [17 bytes data]
* Moved PermanentlyConnection #0 to host whoami.example.com left intact

7. connect from inside the custom network directly to the whoami container and use HTTP
Hostname: a4840a9ff48a
IP: 127.0.0.1
IP: ::1
IP: 10.89.0.2
IP: fe80::5430:f7ff:fec6:2837
RemoteAddr: 10.89.0.13:37862
GET / HTTP/1.1
Host: whoami.example.com
User-Agent: curl/8.13.0
Accept: */*

output when using variant=http3-outside

_________ test HTTP/3 _________
1. connect from outside the custom network and use HTTP/3
Hostname: 71fe521b8b1c
IP: 127.0.0.1
IP: ::1
IP: 10.89.0.2
IP: fe80::d061:94ff:fe28:1967
RemoteAddr: 10.89.0.3:34370
GET / HTTP/1.1
Host: whoami
User-Agent: curl/8.13.0
Accept: */*
Accept-Encoding: gzip
X-Forwarded-For: 10.0.2.15
X-Forwarded-Host: whoami.example.com
X-Forwarded-Port: 443
X-Forwarded-Proto: https
X-Forwarded-Server: 6431b77c3a81
X-Real-Ip: 10.0.2.15


_________ test HTTP2 __________
2. connect from outside the custom network and use HTTP2
Hostname: 71fe521b8b1c
IP: 127.0.0.1
IP: ::1
IP: 10.89.0.2
IP: fe80::d061:94ff:fe28:1967
RemoteAddr: 10.89.0.3:34370
GET / HTTP/1.1
Host: whoami
User-Agent: curl/8.13.0
Accept: */*
Accept-Encoding: gzip
X-Forwarded-For: 10.0.2.15
X-Forwarded-Host: whoami.example.com
X-Forwarded-Port: 443
X-Forwarded-Proto: https
X-Forwarded-Server: 6431b77c3a81
X-Real-Ip: 10.0.2.15


_________ test HTTP ___________
3. connect from outside the custom network and use HTTP
* Host whoami.example.com:80 was resolved.
* IPv6: (none)
* IPv4: 169.254.1.2
*   Trying 169.254.1.2:80...
* Connected to whoami.example.com (169.254.1.2) port 80
* using HTTP/1.x
> GET / HTTP/1.1
> Host: whoami.example.com
> User-Agent: curl/8.13.0
> Accept: */*
> 
* Request completely sent off
Moved Permanently< HTTP/1.1 301 Moved Permanently
< Location: https://whoami.example.com/
< Date: Sun, 25 May 2025 10:51:45 GMT
< Content-Length: 17
< 
{ [17 bytes data]
* Connection #0 to host whoami.example.com left intact

[eriksjolund]

fixed by new Example 2

• Add HTTP/3 example (Example 2) #24

This traefik PR is also needed

• Bump quic-go to v.0.49.0 traefik/traefik#11848