ERR_QUIC_PROTOCOL_ERROR with Caddy(server) and Chrome(client)

[fish fish]

Hello, everyone.

I am seeking for help. 

On the server side, I applied Caddy and enable quic with -quic. My Caddy works on localhost:443

On the client side, I applied Chrome with

google-chrome \

      --user-data-dir=/tmp/chrome-profile \

      --no-proxy-server \

      --enable-quic \

      --origin-to-force-quic-on=localhost:443 \

      https://localhost

and it could not work properly. The webpage showed: ERR_QUIC_PROTOCOL_ERROR.

This is a QUIC packet captured by wireshark and it showed the reason why quic failed: 

A crypto message was received with a mandatory parameter missing

 

how I try to find the problems are as follows.

When I delete --origin-to-force-quic-on=localhost:443

I could open https://localhost but it is not running on QUIC but TLS 1.2 ! like this which showed that there is no problem in CA

and take a look at the response headers, which showed that there is no problem in QUIC headers

 

[Lucas Clemente]

quic-go (which powers Caddy's QUIC) doesn't support connecting to localhost, since there's no server name indication (SNI), as the last line in your Wireshark screenshot says. See our README for details on how you can still try it locally.

Also, I think this list is intended more for discussions of the protocol itself. Feel free to open issues on our Github if you have any other questions concerning our implementation.

On Mon, 6 Mar 2017 at 10:27 fish fish <siyuf...@gmail.com> wrote:

Hello, everyone.

I am seeking for help. 

On the server side, I applied Caddy and enable quic with -quic. My Caddy works on localhost:443

On the client side, I applied Chrome with

google-chrome \

      --user-data-dir=/tmp/chrome-profile \

      --no-proxy-server \

      --enable-quic \

      --origin-to-force-quic-on=localhost:443 \

      https://localhost

and it could not work properly. The webpage showed: ERR_QUIC_PROTOCOL_ERROR.

AND from the wireshark I get this. This is a QUIC packet captured by wireshark it showed the reason why quic failed: 

A crypto message was received with a mandatory parameter missing

how I try to find the problems are as follows.

When I delete --origin-to-force-quic-on=localhost:443

I could open https://localhost but it is not running on QUIC but TLS 1.2 ! like this which showed that there is no problem in CA

and take a look at the response headers, which showed that there is no problem in QUIC headers

 

--
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 post to this group, send email to proto...@chromium.org.
For more options, visit https://groups.google.com/a/chromium.org/d/optout.