You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Jason van Zyl (JIRA)" <ji...@codehaus.org> on 2010/03/30 15:40:23 UTC
[jira] Closed: (MNG-4306) Jetty-client based Wagon
[ http://jira.codehaus.org/browse/MNG-4306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason van Zyl closed MNG-4306.
------------------------------
Resolution: Won't Fix
We're not using the Jetty-based wagon, we are likely to use a Netty-based one through Jeanfrancois async client.
> Jetty-client based Wagon
> ------------------------
>
> Key: MNG-4306
> URL: http://jira.codehaus.org/browse/MNG-4306
> Project: Maven 2 & 3
> Issue Type: New Feature
> Reporter: Jason van Zyl
> Assignee: Benjamin Bentmann
> Fix For: 3.0-alpha-8
>
>
> We need a new high performance Wagon that encapsulates all the features of the current HTTP wagons, but will be the single implementation we use going forward.
> Brian's comments on the features of each Wagon right now:
> Currently the lightweight impl handles NTLMv2 and does a better job
> caching the data when the repository asks for authentication (this one
> uses Sun code). The Sun code has bugs that interfere with uuencoding
> of data in the headers, specifically the passwords. The other wagon
> uses the httpclient, which doesn't support NTLMv2 and doesn't cache
> the data, screwing up the stream observers with repos that need auth.
> It doesn't screw up the data in the headers. So hopefully Jetty will
> support NTLMv2, be smart about handling authenticated repos and not
> screw up the data in the headers.
--
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