Skip to content

middleware: misleading function ContentEncoding does not implement any compression #440

@fredbi

Description

@fredbi

Is your feature request related to a problem? Please describe.

Function ContentEncoding (now negotiate.ContentEncoding) implements the negotiation
of the Content-Encoding header but doesn't do anything with the outcome.

I'd had expected that ContenEncoding does actually something dealing with compression, but it just doesn't.

So either this is a wrongly-headed addition, or an unfinished job. I think we should add real compression middleware on the client and server side and actually use this negotiation.

Describe the solution you'd like

Describe alternatives you've considered

Additional context

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions