[
https://issues.apache.org/jira/browse/AXIS2-2553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12763916#action_12763916
]
Ostap edited comment on AXIS2-2553 at 10/9/09 2:01 AM:
-------------------------------------------------------
Until the bug is fixed you have to change the documentation
http://ws.apache.org/axis2//1_5/http-transport.html#httpsupport
snip...
"You can overwrite the "https" protocol, or use a different protocol for your
SSL client authentication communications if you don't want to mess with regular
https. Find more information at
http://jakarta.apache.org/commons/httpclient/sslguide.html";
The Feature is not working at least since 2007 and there is no sense to raise
the expectations:
definition of custom protocols for SSL connection is almost not possible due
to use of URL Object as wrapper for port and host information in
org.apache.axis2.transport.http.CommonsHTTPTransportSender#writeMessageWithCommons(MessageContext
messageContext, EndpointReference toEPR, OMOutputFormat format) . URL object
is not simply wrapper, in background the protocol will be checked, what causes
the Exception above for unknown protocols.
was (Author: topsilmopsil):
Until the bug is not fixed you have to change the documentation
http://ws.apache.org/axis2//1_5/http-transport.html#httpsupport
snip...
"You can overwrite the "https" protocol, or use a different protocol for your
SSL client authentication communications if you don't want to mess with regular
https. Find more information at
http://jakarta.apache.org/commons/httpclient/sslguide.html";
The Feature is not working at least since 2007 and there is no sense to raise
the expectations:
definition of custom protocols for SSL connection is almost not possible due
to use of URL Object as wrapper for port and host information in
org.apache.axis2.transport.http.CommonsHTTPTransportSender#writeMessageWithCommons(MessageContext
messageContext, EndpointReference toEPR, OMOutputFormat format) . URL object
is not simply wrapper, in background the protocol will be checked, what causes
the Exception above for unknown protocols.
> When using custom protocol (eg myhttps) AxisFault caused by
> MalformedURLException is thrown during web sevice invocation
> ------------------------------------------------------------------------------------------------------------------------
>
> Key: AXIS2-2553
> URL: https://issues.apache.org/jira/browse/AXIS2-2553
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: kernel
> Affects Versions: 1.2, 1.1.1, nightly
> Environment: Windows, JDK 1.4, 1.5
> Reporter: Sergio
> Assignee: Deepal Jayasinghe
> Priority: Critical
> Attachments: patch.jar, patch.txt
>
>
> When custom protocol is used (eg myssl://localhost/WSTest.asmx) we get
> AxisFault caused by MalformedURLException
> because of the problem in the method below. For safe custom url endpoint
> address parsing, you should be using URI and not URL, which
> only allows standard protocols.
> CommonsHTTPTransportSender.writeMessa.writeMessageWithCommons(MessageContext
> messageContext,
> EndpointReference toEPR,
> OMOutputFormat format)
> throws AxisFault {
> try {
>
> URL url = new URL(toEPR.getAddress()); //throws
> MalformedURLException!!!
> .....
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
