[ http://issues.apache.org/jira/browse/XMLRPC-64?page=all ]
Jochen Wiedmann closed XMLRPC-64:
---------------------------------
Resolution: Fixed
The above source is completely different in the current version of Apache
XML-RPC. In particular, a method createTransport() doesn't even exist anymore.
Most possibly, the problem was fixed in the meantime. If not, please reopen.
> DefaultXmlRpcTransportFactory forgets authentication setting when using http
> ----------------------------------------------------------------------------
>
> Key: XMLRPC-64
> URL: http://issues.apache.org/jira/browse/XMLRPC-64
> Project: XML-RPC
> Type: Bug
> Components: Source
> Versions: 2.0
> Reporter: Andreas Sahlbach
>
> We normally use XMLRPC via SSL. But for interprocess communication from
> webapp to webapp on the same server we use a normal HTTP port (bound only to
> localhost, so we can skip the SSL overhead). The XMLRPC port is secured via
> Basic Authentication in both cases.
> I am setting the authentication at the client by creating a
> DefaultXmlRpcTransportFactory, setting the authentication at it and deliver
> it when I am creating the XMLRPC client. The problem is, that if the URL is
> http, no authentication was sent. If I just change the URL to https, the
> authentication was used.
> After some debugging it boild
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
