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:
Two really useful middlewares to decode applied encoding and content charset.
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.