1595269 - HTTP/2.0 still displayed even if HTTP/3.0 is used

Status: RESOLVED WORKSFORME

(DevTools :: Netmonitor, defect, P3)

Description

[YF (Yang)]

What were you doing?

1. Set network.http.http3.enabled to true, restart firefox.
2. Open Devtools - Networks, then open https://http3check.net/.

What happened?

For all requests, messages header display the Version: HTTP/2.0, like HTTP/3 is not working.

Through about:networking#logging, I see like [Parent 9468: Socket Thread]: E/nsHttp HTTP/3.0 304 Not Modified, it works.

What should have happened?

Version: HTTP/3.0 in Devtools - Networks.

Anything else we should know?

since bug 1581637.

Firefox 72.0a1 (2019-11-08).

Comment 1

[Dragana Damjanovic [:dragana]]

It is currently not working. I manage to see the page once, but it is now using h3-24 version. We will update to 24 soon.

Comment 2

[Jan Honza Odvarko [:Honza] (always need-info? me)]

Thanks for the report!

(In reply to Dragana Damjanovic [:dragana] from comment #1)

It is currently not working. I manage to see the page once, but it is now using h3-24 version. We will update to 24 soon.

The same for me, saw it once, but now it doesn't load.

It would be great to have a test case for this so, we can fix it.

Honza

Comment 3

[alex_mayorga]

¡Hola Dragana!

This now seems to work for me on today's Firefox Nightly 74.0a1 (2020-02-05) built from https://hg.mozilla.org/mozilla-central/rev/ee653474267a8b3660c9d70f659b5f655d3ed586

Request URL:https://http3check.net/
Request Method:GET
Remote Address:159.65.253.210:443
Status Code:
200
Version:HTTP/3
Referrer Policy:same-origin

FWIW https://bagder.github.io/HTTP3-test/ has a good list of various test servers but some of them don't even load correctly on Firefox Nightly for me so I'm doubtful on marking this one as FIXED.

Should this bug be broadened or separate ones be filed for each of the other test servers?

¡Gracias!
Alex

Comment 4

[Dragana Damjanovic [:dragana]]

We will update to h3-25 soon. This will include some other fixes as well. (I will retest servers from the list before updating to the new version, that is what I usually do, but the implementations are changing and new bugs may be discovered between updates).

please open separate issues for other problems you see. and always use networking as a component in that way I will see them sooner.

Comment 5

[Dragana Damjanovic [:dragana]]

I have not see this behavior for some time already. I will close the bug, but feel free to reopen if encountered again.

Comment 6

[George [:fozzie]]

I still experience this issue, HTTP/3 is displayed in about:networking but not in the Networking dev tools tab.

Even after several refreshes of the content it still displays as HTTP/2.

Comment 7

[Jan Honza Odvarko [:Honza] (always need-info? me)]

George, we need a test case to fix it. Can you please provide one?

Honza

Comment 8

[George [:fozzie]]

Exact same test case as the one reported in the initial opening of this bug, I'm using the latest version of Firefox Nightly (80.0a1 (2020-06-29) (64-bit)).

Comment 9

[Jan Honza Odvarko [:Honza] (always need-info? me)]

Attachment: image.png

I am attaching a screenshot of what I am seeing on my machine.

Some requests are http/2 some http3
Is that expected?
Or all requests should be http/3?

Honza

Comment 10

[George [:fozzie]]

This is the Developer Tools Network tab for me (no requests are HTTP/3): https://cdn.fozzie.space/2nhq4PWbaQDVdP6B/cd8R9iyNnKm2ZmeF.png

Yet when I go into about:networking the request is shown as HTTP/3: https://cdn.fozzie.space/PMyPQfrmc723MMnh/BKPD4CxNV5WtumSi.png

Comment 11

[Dragana Damjanovic [:dragana]]

so we may have (In reply to george from comment #10)

This is the Developer Tools Network tab for me (no requests are HTTP/3): https://cdn.fozzie.space/2nhq4PWbaQDVdP6B/cd8R9iyNnKm2ZmeF.png

Yet when I go into about:networking the request is shown as HTTP/3: https://cdn.fozzie.space/PMyPQfrmc723MMnh/BKPD4CxNV5WtumSi.png

So we may have a connection to the server that uses http/3 but for request we only use http/2 or 1.1 for a couple reasons.
To figure out that went wrong, can you make a http log for me:
https://developer.mozilla.org/en-US/docs/Mozilla/Debugging/HTTP_logging

(I suggest using a clean profile and do not browse other sites, because the log contains cookies and of course all uri).

Comment 12

[George [:fozzie]]

Brand new profile, only enabled network.http.http3.enabled in about:config. This was after about 3 refreshes incase it needed to grab the Alt-Svc headers: https://cdn.fozzie.space/ykT6h6TquQDJ9VY5/5Ke9aMwULwJUcAsf.moz_log

Comment 13

[Dragana Damjanovic [:dragana]]

For some reason it stop using http3, I do not know from the log why it stop using it or it never uses it.
I know there is a http3 connection, but I do not know the reason why firefox stopped using it. Can you make me a log from the beginning of the session thanks.

Comment 14

[George [:fozzie]]

Just looked into it some more, Kaspersky seems to be blocking all use of the QUIC protocol.

However, I don't know why this isn't logged in the logs and I don't know why it shows up as HTTP/3 in about:networking, does Firefox use HTTP/2 to determine if a site is HTTP/3 compatible? or does it just go off the Alt-Svc header?

Comment 15

[Dragana Damjanovic [:dragana]]

(In reply to george from comment #14)

Just looked into it some more, Kaspersky seems to be blocking all use of the QUIC protocol.

However, I don't know why this isn't logged in the logs and I don't know why it shows up as HTTP/3 in about:networking, does Firefox use HTTP/2 to determine if a site is HTTP/3 compatible? or does it just go off the Alt-Svc header?

about:networking shows all started connections that browser has. "started" mean also we try to connect, even if we do not receive any response from a server (the connection will be closed after some time, and also it will disappear from the about:networking; we are planing to add more stats for QUIC connection in about:networking in the near future).

The log does not start from the beginning, so I see in the log that a connection exist, but I do not see enough log data to say why it is not used.

In firefox: as soon as we get a AltSvc header or a frame, firefox tries to connect to the server and if connecting to the server succeeds following request to the host will use http3, if it fails firefox will continue using http2 or http1.1, whatever sever supports.