[jira] [Resolved] (SANTUARIO-336) Multiple race conditions in the ResolverDirectHttp implementation

["Marc Giger (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SANTUARIO-336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marc Giger resolved SANTUARIO-336.
----------------------------------

    Resolution: Fixed

resolved in r1367609, r1367599, r1367582
                
> Multiple race conditions in the ResolverDirectHttp implementation
> -----------------------------------------------------------------
>
>                 Key: SANTUARIO-336
>                 URL: https://issues.apache.org/jira/browse/SANTUARIO-336
>             Project: Santuario
>          Issue Type: Bug
>          Components: Java
>    Affects Versions: Java 1.4.7, Java 1.5.2
>            Reporter: Marc Giger
>            Assignee: Marc Giger
>             Fix For: Java 1.4.8, Java 1.5.3, Java 2.0.0
>
>
> - The ResolverDirectHttp class uses the old style proxy configuration via System.setProperty(). This is a VM wide setting and affects other VM users. This can not be fixed in 1.4.x because it depends on jdk 1.4 which doesn't support java.net.Proxy on URLConnection.openConnection().
> - The ResolverDirectHttp switches back the old proxy configuration if the resource could successfully fetched but if an exception happens the new proxy will still be set.
> - Additionally there is an error when Proxy-Authentication was used. The implementation provides support for Basic Authentication but doesn't set the Authentication type on the header:
> Proxy-Authorization: <base64encodedUsernameAndPassword>
> but should be
> Proxy-Authorization: Basic <base64encodedUsernameAndPassword>

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira