synapse-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Asankha C. Perera (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (SYNAPSE-186) Better support for HTTP in the NIO transport
Date Sun, 24 May 2009 06:24:45 GMT

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

Asankha C. Perera resolved SYNAPSE-186.
---------------------------------------

    Resolution: Fixed

Synapse now acts as a general proxy for HTTP as per most of RFC 2616 with SYNAPSE-551

I am not sure I understand the 302 case exactly.. could you give an example of the scenario
& expected behavior and re-open this (or open a new JIRA) if there is anything pending

> Better support for HTTP in the NIO transport
> --------------------------------------------
>
>                 Key: SYNAPSE-186
>                 URL: https://issues.apache.org/jira/browse/SYNAPSE-186
>             Project: Synapse
>          Issue Type: Bug
>          Components: Transports
>    Affects Versions: 1.1
>            Reporter: Paul Fremantle
>            Assignee: Asankha C. Perera
>             Fix For: FUTURE
>
>
> We need to support things such as 302 redirects in the client and HEAD requests in the
server.
> Generally I'd like to see the NIO transport improved until we can fully support HTTP
- e.g. as an HTTP Proxy

-- 
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


Mime
View raw message