QUIC disabled when Updated chrome to version 86

[jian chen]

Hi,

Recently I updated my chrome to stable 86, then I used it as QUIC client to test our QUIC server(based on chromium87)，unfortunately i found that QUIC server did not receive any QUIC related request. This make me confused. By the way, before I updated chrome, I used QUIC by sending a response header:

            alt-svc: quic=":443";ma=2592000;v="73,71,51,50,46,43"

and that worked alway well.

Any idea about the reason?

[David Schinazi]

Hello,

You're using the legacy Alt-Svc format that we're removing support for.

Instead, I'd suggest sending this format:

alt-svc: h3-Q050=":443"; ma=2592000,h3-29=":443"; ma=2592000,h3-27=":443"; ma=2592000,h3-T051=":443"; ma=2592000,h3-T050=":443"; ma=2592000,h3-Q046=":443"; ma=2592000,h3-Q043=":443"; ma=2592000

David

--
You received this message because you are subscribed to the Google Groups "QUIC Prototype Protocol Discussion group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to proto-quic+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/proto-quic/a2ad88d1-def7-4b9a-a1b6-8655d76ade59n%40chromium.org.

[jian chen]

Thanks for your answer, I used the alt-svc format you gave and it works. Another question is chrome always use Q050, is there any way to change chrome settings so that I can test IETF QUIC? 

[David Schinazi]

Great!

To force Chrome to use a specific version of QUIC, you can start it with the quic-version command-line flag. For example, to force the latest IETF QUIC draft: --quic-version=h3-29

David

[puneet kumar]

Hi All,

I would like to know if there is any method QUIC adopts to counter port scan attacks?

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/proto-quic/CAPDSy%2B6pEL-8am-fcq4dA-WywNSTV4QR1m-ZNbbrXedd4zjhQg%40mail.gmail.com.

[jian chen]

I tried to add quic-version command-line flag like this:

           google-chrome --enable-quic --quic-version=h3-29 --no-proxy-server --origin-to-force-quic-on=www.test.xxx.com:443 --host-resolver-rules='MAP www.test.xxx.com:443 127.0.0.1:443' https://test.xxx.com

but it still use gQUIC version. Is there any error?

Jian

[jian chen]

I have always been using stable version of chrome, is that  because  quic-version command-line flag is only supported in Chrome Canary？

在2020年10月14日星期三 UTC+8 下午11:06:45<dschina...@gmail.com> 写道：

[David Schinazi]

--quic-version should work on all builds and channels of Chrome, and Chromium.

David