[
https://issues.apache.org/jira/browse/SYNAPSE-397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12629283#action_12629283
]
Andreas Veithen commented on SYNAPSE-397:
-----------------------------------------
> But using the full URL in a POST and the "Host" header allows us to go
> through proxies for outgoing connections
Going through a proxy requires the host/port used in the URL to be different
from the host/port the transport connects to. Since this is not supported by
the transport, how could the POST_TO_PATH property be used to go through a
proxy?
> 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]
