[
http://jira.codehaus.org/browse/XFIRE-920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Greg Kempe updated XFIRE-920:
-----------------------------
Attachment: proxyauth.patch
In addition, CommonsHttpMessageSender.getCredentials() unnecessarily sets
preemptive authentication for regular (non-proxy) credentials, resulting in
WARN log messages.
Patch against 1.2.5 attached.
> Http Proxy authentication not working
> -------------------------------------
>
> Key: XFIRE-920
> URL: http://jira.codehaus.org/browse/XFIRE-920
> Project: XFire
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.2.5
> Reporter: Andreas Raquet
> Assignee: Dan Diephouse
> Attachments: CommonsHttpMessageSender.java, proxyauth.patch
>
>
> http proxy authentication is not working if one uses a
> org.codehaus.xfire.client.Client. Username and password were provided as
> stated in the documentation, but they never arrive in the http message.
> According to bug XFIRE-809, this should be fixed since 1.2.4, but it still
> does not work in 1.2.5. (I cannot reopen XFire-809)
> After some debugging I found CommonsHttpMessageSender to be the culprit. In
> the createClient() method, it sets the proxy credentials as part of the
> client state. In the open() method - right after calling createClient() - it
> creates a new HttpState, overwriting the original client state that contained
> the proxy credentials.
> To fix this, I moved the initialization of the proxy credentials from
> createClient() to open(), right where the http credentials are set. This
> setup works fine for me.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
