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

Content-Encodings should be self-describing #21

Closed
bsdphk opened this issue Nov 1, 2016 · 2 comments · Fixed by #430
Closed

Content-Encodings should be self-describing #21

bsdphk opened this issue Nov 1, 2016 · 2 comments · Fixed by #430

Comments

@bsdphk
Copy link

bsdphk commented Nov 1, 2016

As part of the discussion about the Encryption specification we discussed how Content-Encodings can or should take parameters from HTTP headers.

The consensus was that they shouldn't.

Whatever information a C-E may need should be inside the body of the object, just like the GZIP header etc.

We should document this as a rule, if we ever do a HTTP[1].ter

@reschke
Copy link
Contributor

reschke commented Nov 15, 2016

+1, except for the constraint: "when possible". In the case of the encryption coding, it's clearly necessary to have the actual key information needed for description outside the payload.

@royfielding
Copy link
Member

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging a pull request may close this issue.

4 participants