[SYNAPSE-587] NHTTP Transport Does Not Handle Responses With No Content-Type Header Properly

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.2, NIGHTLY
• Fix Version/s: 2.0
• Component/s: Transports
• Environment: Any
• Assignee: Hiranya Kasub Jayathilaka
• Reporter: Hiranya Kasub Jayathilaka
• Created: 01/Oct/09 07:44
• Updated: 19/Nov/09 10:58
• Resolved: 19/Nov/09 10:58

Description

Currently the NHTTP transport would assume an empty payload for response messages which do not have the HTTP Content-Type header. According to the HTTP/1.1 specification this should be handled as follows.

<quote>
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".
</quote>