You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If the content-coding of an entity in a request message is not acceptable to the origin server, the server SHOULD respond with a status code of 415 (Unsupported Media Type).
More specifically, if request compression is disabled, or a non-supported coding is used, we should return a 415 error. This could live in NIO's NIOHTTPRequestDecompressor, but that wouldn't handle the case where the handler is never attached (aka request decompression is disabled), so we should probably handle it in the DefaultResponder.
The text was updated successfully, but these errors were encountered:
According to RFC 2616 - 14.11 Content-Encoding:
More specifically, if request compression is disabled, or a non-supported coding is used, we should return a 415 error. This could live in NIO's NIOHTTPRequestDecompressor, but that wouldn't handle the case where the handler is never attached (aka request decompression is disabled), so we should probably handle it in the
DefaultResponder
.The text was updated successfully, but these errors were encountered: