https://bz.apache.org/bugzilla/show_bug.cgi?id=58027
--- Comment #11 from Sebb <[email protected]> --- Turns out that problem is that the response does not include a Content-Type. According to RFC 2616 section 7.2.1 >>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".<< The server that is returning the content is misbehaving. It ought to include a Content-Type so the client knows what to do without requiring additional heuristics. -- You are receiving this mail because: You are the assignee for the bug.
