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
Found an issue when trying to use CORS via HTTP3 (lucas-clemente/quic-go) that the "allow-control-request-headers" was being interpreted as the "allow-control-expose-headers" when the request was coming from chrome 86.0.4240.111 and firefox 82.0.
I've checked the most recent draft-ietf-quic-qpack-19 and found in the static table that it should be coming in as index 80 but looking here it's paired with index 79.
The text was updated successfully, but these errors were encountered:
Found an issue when trying to use CORS via HTTP3 (lucas-clemente/quic-go) that the "allow-control-request-headers" was being interpreted as the "allow-control-expose-headers" when the request was coming from chrome 86.0.4240.111 and firefox 82.0.
I've checked the most recent draft-ietf-quic-qpack-19 and found in the static table that it should be coming in as index 80 but looking here it's paired with index 79.
The text was updated successfully, but these errors were encountered: