Mailing-List: contact dev-help@synapse.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@synapse.apache.org
Message-ID: <434189176.1258091019619.JavaMail.jira@brutus>
Date: Fri, 13 Nov 2009 05:43:39 +0000 (UTC)
From: "Asankha C. Perera (JIRA)" <jira@apache.org>
To: dev@synapse.apache.org
Subject: [jira] Reopened: (SYNAPSE-587) NHTTP Transport Does Not Handle
 Responses With No Content-Type Header Properly
In-Reply-To: <853758553.1254383063592.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Asankha C. Perera reopened SYNAPSE-587:
---------------------------------------


Hi Hiranya

This fix has broken the raw HTTP support Synapse had.. The HTTP spec talks only about "message containing an entity-body..." but there are responses etc that does not contain an entity body, in which case this creates a serious bug as shown in http://markmail.org/thread/o33ypagpv7txikrb

Could you fix this back to ensure that REST/POX and raw HTTP support will work as before?

thanks
asankha

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