Middleware to decode encoding and charset #156
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Two really useful middlewares to decode applied encoding and content charset.
content-coding
meta data for plugins quixdb/squash#197)deflate
bug on IE (see https://en.wikipedia.org/wiki/HTTP_compression)It will require some documentation and tests. The logic is quite tricky, especially for
decode
as remaining encodings are reversed back in the headers.I couldn't find anything more appropriate than
501 Not Implemented
to indicate the lack of support for an encoding or charset.The typical use case is on the top of an app or for an upload processing:
The squash integration must be opt-in with fallback on the basic converters.