synapse-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sivajothy Vanjikumaran (JIRA)" <j...@apache.org>
Subject [jira] [Issue Comment Deleted] (SYNAPSE-992) Adding the default Content-Type when there is no body in the response
Date Tue, 09 Sep 2014 06:24:30 GMT

     [ https://issues.apache.org/jira/browse/SYNAPSE-992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Sivajothy Vanjikumaran updated SYNAPSE-992:
-------------------------------------------
    Comment: was deleted

(was: Please find the patch that contain the fix for above mention issue.
)

> 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_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-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org


Mime
View raw message