We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
6
However, multiple trailer sections interleaved with content have only been deployed as frame extensions.
Trailers that come after the body has well-defined semantics (i.e. metadata applicable to the entire body).
Interleaved, mid-stream trailers are considered and implemented as extensions, and maybe we should delay adding them to the core semantics.
This is however an important topic for HTTPAPI, IMO.
The text was updated successfully, but these errors were encountered:
See related mailing list thread at https://lists.w3.org/Archives/Public/ietf-http-wg/2021JanMar/0070.html.
Sorry, something went wrong.
Discussed at Feb 21 interim; sentiment is to remove it; @royfielding to create a PR.
royfielding
Successfully merging a pull request may close this issue.
6
Trailers that come after the body has well-defined semantics (i.e. metadata applicable to the entire body).
Interleaved, mid-stream trailers are considered and implemented as extensions, and maybe we should delay adding them to the core semantics.
This is however an important topic for HTTPAPI, IMO.
The text was updated successfully, but these errors were encountered: