You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@synapse.apache.org by "Asankha C. Perera (JIRA)" <ji...@apache.org> on 2009/05/24 07:36:45 UTC
[jira] Resolved: (SYNAPSE-386) Responses with HTTP Status codes
don't always get returned to the client.
[ https://issues.apache.org/jira/browse/SYNAPSE-386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Asankha C. Perera resolved SYNAPSE-386.
---------------------------------------
Resolution: Fixed
Assignee: Asankha C. Perera
Fixed with SYNAPSE-551
> Responses with HTTP Status codes don't always get returned to the client.
> -------------------------------------------------------------------------
>
> Key: SYNAPSE-386
> URL: https://issues.apache.org/jira/browse/SYNAPSE-386
> Project: Synapse
> Issue Type: Bug
> Components: Transports
> Affects Versions: NIGHTLY
> Reporter: Leander Harding
> Assignee: Asankha C. Perera
>
> When using an HTTP GET endpoint, if the destination server returns an "unexpected" (as defined by ClientHandler.responseRecieved; e.g. 304 Not Modified) status code, and doesn't return any content, but does set a Content-Type, the message never gets returned to any mediator sequence.
--
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