[
https://issues.apache.org/jira/browse/SYNAPSE-587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12779868#action_12779868
]
Hiranya Jayathilaka commented on SYNAPSE-587:
---------------------------------------------
Hi Asankha,
I have implemented a possible fix in the 1.3 branch for the issues mentioned in
the above mail thread. I have tested the new fix with some HTTP 204 responses
and it seems to be working. The original problem that I tried to solve is also
no longer there. Could you please verify the REST scenarios are working as
expected?
Thanks,
Hiranya
> NHTTP Transport Does Not Handle Responses With No Content-Type Header Properly
> ------------------------------------------------------------------------------
>
> Key: SYNAPSE-587
> URL: https://issues.apache.org/jira/browse/SYNAPSE-587
> Project: Synapse
> Issue Type: Bug
> Components: Transports
> Affects Versions: 1.2, NIGHTLY
> Environment: Any
> Reporter: Hiranya Jayathilaka
> Assignee: Hiranya Jayathilaka
> Fix For: 1.3
>
>
> 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>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
