https://bz.apache.org/bugzilla/show_bug.cgi?id=60190
Philippe Mouawad <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO --- Comment #4 from Philippe Mouawad <[email protected]> --- Hello, How about not adding this anymore if not set and having a property that allows to do that ? post_add_content_type_if_missing=false What is the risk ? As per: https://www.w3.org/Protocols/rfc2616/rfc2616-sec7.html Any HTTP/1.1 message containing an entity-body SHOULD include a Content-Type header field defining the media type of that body. If and only if the media type is not given by a Content-Type field, the recipient MAY attempt to guess the media type via inspection of its content and/or the name extension(s) of the URI used to identify the resource. If the media type remains unknown, the recipient SHOULD treat it as type "application/octet-stream". Thanks -- You are receiving this mail because: You are the assignee for the bug.
