localhost running on chromium not chrome Followup #145

[abnvsally]

I tried to use chrome and the commands you have mentioned to open the client in the browser but it does-not work. I tried to open the client using the chromium browser built from the chromium source code and localhost works in that. I do not even need to generate fingerprints for the certificate command to run client side in chromium. The commands for running chrome and chromium are mentioned below.

When I connect the client side using chrome I see TCP packets getting called from the browser. The reset packets are TCP as well. There are no UDP/QUIC packets coming from chrome browser and the local host gives site cannot be reached error. I have tried https://127.0.0.1:4433 as well as https://localhost:4433. Both show the same behavior.

I can see HTTP/3 when I use the curl command. The output is as follows: -

curl --http3 -I https://localhost:4433/
HTTP/3 200
server: aioquic/0.9.7
date: Fri, 30 Oct 2020 17:24:42 GMT
content-length: 1580
content-type: text/html; charset=utf-8

I use these commands for the chrome browser: -

/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome
--enable-quic
--ignore-certificate-errors-spki-list=BSQJ0jkQ7wwhR7KvPZ+DSNk2XTZ/MS6xCbo9qu++VdQ= --origin-to-force-quic-on=localhost:4433 \ https://localhost:4433/

I use the following commands for the chromium browser: -

out/Default/Chromium.app/Contents/MacOS/Chromium
--enable-quic
--origin-to-force-quic-on=localhost:4433 \ https://localhost:4433/

Wireshark pcap attached for reference to see the chrome's behavior.

QUIC_Error.pcapng.zip

Please let me know if I'm missing something here. Thanking you in anticipation.

[jlaine]

It works fine using Chrome 88 on Linux using the instructions in #127

Chromium doesn't work, I'm not convinced QUIC / HTTP3 support is built in.