Skip to content

Content-Encodings should be self-describing #21

@bsdphk

Description

@bsdphk

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

Metadata

Metadata

Assignees

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions