Web UI HTTP/3 , Option to change max-age in Alt-Svc

[ssrahul96]

Prerequisites

• I have checked the Wiki and Discussions and found no answer

• I have searched other issues and found no duplicates

• I want to report a bug and not ask a question

Operating system type

Linux, Other (please mention the version in the description)

CPU architecture

AMD64

Installation

Docker

Setup

On one machine

AdGuard Home version

v0.108.0-b.17

Description

What did you do?

#4986 let the browser know that the server supports h3 by adding Alt-Svc header, default value of 24h is taken by defauly

Expected result

Ability to set max-age for Alt-Svc in config file

Actual result

Screenshots (if applicable)

Additional information

[flavorgold1]

What is the use of the max-age setting?

[ssrahul96]

@flavorgold1 , in simple words you can keep it as cache, by default the max-age is set to 24h,Within that 24h, the browser try to make all the request in h3.

Consider if you opening the server after a day or 2 (beyond max-age time), the browser would start with h1 / h2, again the process repeats

[flavorgold1]

@ssrahul96, to add to this conversation, I think there needs to be increased awareness of HTTPS DNS records.

As an example: https://dns.google/query?name=google.com&rr_type=HTTPS

For more info:

(1) https://blog.cloudflare.com/speeding-up-https-and-http-3-negotiation-with-dns/

(2) https://developer.mozilla.org/en-US/docs/Glossary/https_rr

In Safari, when you enable the Developer Menu, and then enable HTTP3 under Experimental Features: it seems to automatically jump to HTTP3 -- I believe, by reading these HTTPS DNS records that specify that you have h3 enabled.

Other browsers are also using these records, increasingly.

[daryll-swer]

Is this related as to why QUIC isn't working for the Web UI?

2022/10/15 01:20:04.138384 [info] DNS cache is enabled
2022/10/15 01:20:04.138424 [info] MaxGoroutines is set to 300
2022/10/15 01:20:04.138453 [info] Fastest IP is enabled
2022/10/15 01:20:04.138493 [info] Creating the UDP server socket
2022/10/15 01:20:04.138758 [info] Listening to udp://[::]:53
2022/10/15 01:20:04.138781 [info] Creating a TCP server socket
2022/10/15 01:20:04.138937 [info] Listening to tcp://[::]:53
2022/10/15 01:20:04.138958 [info] Creating a TLS server socket
2022/10/15 01:20:04.139075 [info] Listening to tls://[::]:853
2022/10/15 01:20:04.139105 [info] Creating a QUIC listener
2022/10/15 01:20:04.139974 [info] Listening to quic://[::]:853
2022/10/15 01:20:04.140278 [info] Entering the tls listener loop on [::]:853
2022/10/15 01:20:04.140385 [info] Entering the DNS-over-QUIC listener loop on [::]:853
2022/10/15 01:20:04.140282 [info] Entering the tcp listener loop on [::]:53
2022/10/15 01:20:04.140299 [info] Entering the UDP listener loop on [::]:53
00:45:32.571151 [info] Entering the DNS-over-QUIC listener loop on [::]:853
2022/10/15 00:45:32.571674 [info] Entering the UDP listener loop on [::]:53
2022/10/15 00:49:08.817940 [info] got error when accepting a new QUIC stream: APPLICATION_ERROR
2022/10/15 00:49:08.873857 [info] got error when accepting a new QUIC stream: Application error 0x1
2022/10/15 00:49:08.919082 [info] got error when accepting a new QUIC stream: Application error 0x1

[ainar-g]

@daryll-swer, please use Discussions for debug help. Thanks.

The error looks like a client error, but you can enable debug logs to see more info.