Mailing-List: contact dev-help@synapse.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@synapse.apache.org
Message-ID: <621130508.1243143405580.JavaMail.jira@brutus>
Date: Sat, 23 May 2009 22:36:45 -0700 (PDT)
From: "Asankha C. Perera (JIRA)" <jira@apache.org>
To: dev@synapse.apache.org
Subject: [jira] Resolved: (SYNAPSE-386) Responses with HTTP Status codes
 don't always get returned to the client.
In-Reply-To: <414574945.1214961045071.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-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