afrind
afrind
h2 specification for h2c: https://tools.ietf.org/html/rfc7540#section-8.1.1
I think the kind of blocked events you are talking about are the most likely to be of general use, since one doesn't really need to be a QPACK expert...
Even the updated RFC 9110 has the following: > A 204 response is terminated by the end of the header section; it cannot contain content or trailers. Can you send...
Can you migrate to HTTP/2 so an individual request failure doesn’t preclude connection re-use? From: Mats Attnäs ***@***.***> Reply-To: facebook/proxygen ***@***.***> Date: Tuesday, September 20, 2022 at 1:32 AM To:...
From OpenRTB: > To express a “no-bid”, the options are to return an empty response with HTTP 204. Alternately if the bidder wishes to convey to the exchange a reason...
Is there any more to the log? There's not much to go on here
Closing old pull request. While WebSocket support might be suboptimal, WebTransport (new hotness) is supported as a first class construct.
I usually skip the --protocol arg completely -- does that fix your issues? I know chrome -> hq server is working.
If you just run `./hq --mode=server --cert= --key= --port 8443 -v 4` And hit with chrome, what's the server output?
Relevant log line: `I1109 12:34:47.255358 7858 FizzAcceptorHandshakeHelper.cpp:153] Fizz handshake error with (peer=[::1]:45860, local=[::1]:6667) after 6 ms; 547 bytes received & 2120 bytes sent: fizz::FizzException: received alert: certificate_unknown, in state ExpectingFinished`...