Microsoft.AspNet.WebApi.MessageHandlers.Compression icon indicating copy to clipboard operation
Microsoft.AspNet.WebApi.MessageHandlers.Compression copied to clipboard

Published 20 hours ago • verified publisher icon azzlack

Explicitly Reject Identity

Open sburtonctr opened this issue 8 years ago • 0 comments

If the client refused all schemes through "identity;q=0" or *;q=0. I am still getting a non-compressed response instead of a 406 - Not Acceptable exception.

I also noticed that the Content-Encoding: identity is missing when a valid non-compressed response is returned. The spec: "https://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.3" is a little confusing, if the Content-Encoding should all ways returning with Content-Coding: Identity if compression is missing, or if Accept-Encoding: identity is a valid content negotiation. Just thought I would bring it up. Thanks for this library.

sburtonctr avatar Mar 20 '17 15:03 sburtonctr