Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

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

Jump to bottom

Support multipart/byteranges for 206 responses #3725

Open
handrews opened this issue Apr 20, 2024 · 0 comments
Open

Support multipart/byteranges for 206 responses #3725

handrews opened this issue Apr 20, 2024 · 0 comments
Assignees
@handrews
Labels
media and encoding Issues regarding media type support and how to encode data (outside of query/path params)
Milestone
v3.3.0

Comments

@handrews
Copy link
Member

RFC 9110 §14.6 defines the multipart/byteranges media type for use in 206 (Partial Content) responses. We should see what, if anything, is needed to support it. Probably something involving the Encoding Object.

Some clients apparently used a not-entirely-compatible multipart/x-byteranges, but I'd argue that RFC 9110 carries enough weight that we should support multiparte/byteranges even if the old x- type is currently more broadly used.
@handrews handrews added the media and encoding Issues regarding media type support and how to encode data (outside of query/path params) label Apr 20, 2024
@handrews handrews self-assigned this Apr 21, 2024
@handrews handrews added this to the v3.2.0 milestone Apr 21, 2024
@handrews handrews modified the milestones: v3.2.0, v3.3.0 Nov 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@handrews handrews

Labels
media and encoding Issues regarding media type support and how to encode data (outside of query/path params)
Projects
None yet
Milestone
v3.3.0
Development

No branches or pull requests
1 participant
@handrews