http-extensions
http-extensions copied to clipboard
HTTP Extensions in progress
This seems like another good candidate for a structured format. Maybe something we can add to the [retrofitted structured headers draft](https://httpwg.org/http-extensions/draft-ietf-httpbis-retrofit.html) as a new set of mapped fields?
This PR is a WIP while waiting on data to show us that this is the correct approach. Until https://github.com/httpwg/http-extensions/pull/1348, the spec mistakenly didn't define the same-site-ness to include the...
SM2/SM3 are Chinese cryptographic algorithms: SM3 (hash function) and SM2 (public-private key cryptography), widely used in China, will you support them?
It'd be nice if there were an appendix summarising the changes. We do this for most updates.
Closes #2352 Summarizes all the major changes from 6265bis, replacing the existing draft-by-draft change log.
I think something is wrong here (why does it expires in a year?) - [2.1.5.2. ](https://httpwg.org/http-extensions/draft-ietf-httpbis-compression-dictionary.html#section-2.1.5.2)[Versioned Directories](https://httpwg.org/http-extensions/draft-ietf-httpbis-compression-dictionary.html#name-versioned-directories) A response that contained a response header: > Use-As-Dictionary: match="/app/*/main.js" Would match main.js...
minimalist attempt at a fix for #2791
I don't believe this example given in [8.8.6. ](https://www.ietf.org/archive/id/draft-ietf-httpbis-rfc6265bis-14.html#section-8.8.6)[Top-level requests with "unsafe" methods](https://www.ietf.org/archive/id/draft-ietf-httpbis-rfc6265bis-14.html#name-top-level-requests-with-uns) particularity well reflects the situation that precipitated the behavior described in [5.5.7.2. ](https://www.ietf.org/archive/id/draft-ietf-httpbis-rfc6265bis-14.html#section-5.5.7.2)["Lax-Allowing-Unsafe" enforcement](https://www.ietf.org/archive/id/draft-ietf-httpbis-rfc6265bis-14.html#name-lax-allowing-unsafe-enforce): > For example,...
A minor typographical fix and slight rephrasing of limitations of current query-embedded-in-request-URI method.
Spec: https://www.rfc-editor.org/rfc/rfc9535.html - how to augment the existing media type definition for QUERY (do we need to? - what response format to use? (application/json)?