[
https://issues.apache.org/jira/browse/SYNAPSE-397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12613515#action_12613515
]
Asankha C. Perera commented on SYNAPSE-397:
-------------------------------------------
> Since the NIO HTTP transport doesn't support proxies, the behavior described
> in this issue is clearly a violation of the HTTP protocol specifications
> (both 1.0 and 1.1) and the absolute path should always be used.
Yes, I agree.. infact, I replied this same way to the user who raised this
issue.. But using the full URL in a POST and the "Host" header allows us to go
through proxies for outgoing connections
> Note that because of requirement (3), this never caused problems before.
However, we have had some issues in the past (e.g.
http://markmail.org/message/deymz7pkatpsozz5) where HTTP 1.1 servers had issues
with this. Since this is an optional property, it would be useful to only those
who require and need it.
> Make it possible for a user to specify that a http/s POST should use only the
> PATH segment instead of the default full URL
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: SYNAPSE-397
> URL: https://issues.apache.org/jira/browse/SYNAPSE-397
> Project: Synapse
> Issue Type: Improvement
> Components: Transports
> Affects Versions: 1.2
> Reporter: Asankha C. Perera
> Assignee: Asankha C. Perera
> Priority: Minor
> Fix For: 1.3
>
>
> Support a new Axis2 message context property POST_TO_PATH (similar to the
> 'FORCE_HTTP_1.0' property) so that a http/s POST would be of the form
> POST /somepath HTTP/1.x
> instead of
> POST http://host:port/somepath HTTP/1.x
--
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
