[
https://issues.apache.org/jira/browse/SYNAPSE-992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14139926#comment-14139926
]
Hiranya Jayathilaka commented on SYNAPSE-992:
---------------------------------------------
I'm not entirely confident about this fix. All this content type inference code
is guarded by an if condition right now:
if (expectEntityBody) {
...
}
So perhaps a better solution is to set the expectEntityBody to false to cover
your scenario (Content-Length = 0; Content-Type = null;). This is a vert
specific case, and we can easily check for it and set the boolean value to
false early in the flow. Can you please look into that option please? Take a
look at the TargetHandler#isResponseHaveBodyExpected() method.
> Adding the default Content-Type when there is no body in the response
> ---------------------------------------------------------------------
>
> Key: SYNAPSE-992
> URL: https://issues.apache.org/jira/browse/SYNAPSE-992
> Project: Synapse
> Issue Type: Bug
> Components: Transports
> Affects Versions: 2.1
> Reporter: Sivajothy Vanjikumaran
> Assignee: Hiranya Jayathilaka
> Priority: Critical
> Labels: patch
> Fix For: FUTURE
>
> Attachments: Synapse_2_2_0_SNAPSHOT_SYNAPSE-992.diff
>
>
> When there is no content type in the response synapse set the default content
> type as "application/octet-stream".
> The HTTP Spec only talks about dealing with Content-Types and assuming
> "application/ocet-stream" for messages, containing an entity-body [1]. As we
> are not providing an entity body, the ESB should not infer a Content-Type.
> Instead of, the ESB just should pass through the response to the client
> without adding a Content-Type.
> [1] http://www.w3.org/Protocols/rfc2616/rfc2616-sec7.html#sec7.2.1
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org
