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.

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

Transfer coding for compression won't work #115

Closed
svgeesus opened this issue Aug 25, 2022 · 4 comments · Fixed by #122
Closed

Transfer coding for compression won't work #115

svgeesus opened this issue Aug 25, 2022 · 4 comments · Fixed by #122
Labels
Range Request Solution includes something specific to range-request method

Comments

@svgeesus
Copy link
Contributor

Originally raised by Martin Thomson

The use of transfer coding for compression won't work in most cases. Transfer coding isn't available in all versions of HTTP.

@svgeesus svgeesus mentioned this issue Aug 25, 2022
8 tasks
@garretrieger garretrieger added the Range Request Solution includes something specific to range-request method label Sep 9, 2022
@garretrieger
Copy link
Contributor

The spec states the the server must support either Content-Encoding or Transfer-Encoding. This should allow it to work with HTTP/1.1 through HTTP/3 servers. Realistically I would expect most implementations to use content-encoding.

@garretrieger
Copy link
Contributor

Maybe a better way would be to always require "Content-Encoding" and have "Transfer-Encoding" be optional since a server that only supports "Transfer-Encoding" doesn't make much sense.

@svgeesus
Copy link
Contributor Author

I agree that specifying Content-Encoding in the spec would be best. Must admit I was unaware that Transfer Coding had been dropped.

@martinthomson does that sound good to you?

@martinthomson
Copy link
Member

Yeah, I would just drop any mention of transfer coding.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Range Request Solution includes something specific to range-request method
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants