#15 Reject request with 415 Unsupported Media Type

open
5
2013-05-07
2012-07-08
Hamish McWilliam
No

In RFC 2616 "Hypertext Transfer Protocol -- HTTP/1.1" the mechanism for rejecting an unsupported encoding type is described. If the "Content-Encoding" and/or "Transfer-Encoding" are not recognized or are not supported the server should return a "415 Unsupported Media Type". This allows the client to retry the request with an alternative encoding (see http://search.cpan.org/dist/SOAP-Lite/lib/SOAP/Transport.pod#COMPRESSION for an client supporting this).

Given that other filters may support alternative encoding types, this would have to be implemented with an option to enable/disable 415 based rejection of encoded requests.

Discussion

    • assigned_to: Sean Owen --> Norbert Bartels
    • Group: --> Next Release (example)