You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I built an HTP3 service using http3-server. c and used firefox to access it without any issues. However, accessing it using Chrome or msedge would result in errors. Through wireshark packet capture, it was found that the quick handshake failed. The first initial packet sent by the HTP3 service, Wireshark decoding, failed. Has anyone encountered this problem
The text was updated successfully, but these errors were encountered:
Did you add SSLKEYLOGFILE file? I had the same issue. I fixed it by turning off "quic.reassemble_crypto_out_of_order" in wireshark. Wireshark->preferences->protoocl->QUIC. And I also set "--wire-version" to 1 when I use quiche client. Hope this is helpful to you.
Did you add SSLKEYLOGFILE file? I had the same issue. I fixed it by turning off "quic.reassemble_crypto_out_of_order" in wireshark. Wireshark->preferences->protoocl->QUIC. And I also set "--wire-version" to 1 when I use quiche client. Hope this is helpful to you.
Thank you for your reply. I have added the SSLKEYLOGFILE file. I use Chrome to access the HTTP3 service on the public network through Quic, and there is no problem displaying it through Wireshark packet capture. I think it's because cloudflare's quiche does not support parsing Chrome's Quic protocol
I built an HTP3 service using http3-server. c and used firefox to access it without any issues. However, accessing it using Chrome or msedge would result in errors. Through wireshark packet capture, it was found that the quick handshake failed. The first initial packet sent by the HTP3 service, Wireshark decoding, failed. Has anyone encountered this problem
The text was updated successfully, but these errors were encountered: