-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Closed
Description
I’m trying to connect to a quic-go server from Chrome on localhost with a self-signed certificate. It either fails with a TLS error (unknown certificate
), or doesn’t connect at all.
I’ve tried both my own test server as well as the example
server in this repo, with the same results. When run with the -tcp
flag, the example
server will happily serve content via HTTP/1.1, but Chrome refuses to open a QUIC connection.
I’ve tried the following matrix with both the example
server and my own server:
- Chrome (91.0.4472.114)
- Chrome Canary (93.0.4552.0)
- With and without the
--origin-to-force-quic
flag - With and without the
--allow-insecure-localhost
flag
The error message from Chrome, with --origin-to-force-quic
enabled:
Is there some known incompatibility between Chrome and quic-go? Am I missing something?
Metadata
Metadata
Assignees
Labels
No labels