[jira] Commented: (MNG-4211) [regression] proxy access broken between maven version 2.0.10 and 2.1. Probably due to addition of wagon 1.0-beta-4+

["Robert Glover Jr (JIRA)" <ji...@codehaus.org>]

    [ http://jira.codehaus.org/browse/MNG-4211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=255276#action_255276 ] 

Robert Glover Jr commented on MNG-4211:
---------------------------------------

By good luck,  an associate of mine seems to have located the specific reason why Maven firewall "broke" (for some of us) when Maven 2.1.0 was released.  The problem can be seen if a debugging proxy is used to intercept and examine the request header that is sent outbound from Maven 2.1.0.  In earlier versions the request header simply stated the java version.  However the request header sent by Maven 2.1.0 says something to the effect of "Maven Apache.. etc.".
   If a debugging proxy is used to change the text of the request head back to what it was in  Maven 2.0.9 and earlier, the problem with the firewall disappears and Maven 2.1.0 works again through a firewall.
   So, this sounds like it should be almost trivially simple for the Maven developers to "fix" so as to provide backwards compatibility in Maven 2.1.0 and above.  I.e., add an option to send the same request header that Maven was sending in Maven 2.0.9 and earlier.
  I hope someone on the Maven developer team reads this and can implement a quick fix.  It is so frustrating to be forced to use Maven 2.0.9 instead of all the goodness in Maven 2.1.0, not to mention Maven 3.

> [regression] proxy access broken between maven version 2.0.10 and 2.1. Probably due to addition of  wagon 1.0-beta-4+
> ---------------------------------------------------------------------------------------------------------------------
>
>                 Key: MNG-4211
>                 URL: http://jira.codehaus.org/browse/MNG-4211
>             Project: Maven 2 & 3
>          Issue Type: Bug
>          Components: Artifacts and Repositories
>    Affects Versions: 2.1.0, 2.2.0
>         Environment: WinXP SP2
>            Reporter: Robert Glover Jr
>            Priority: Blocker
>             Fix For: Issues to be reviewed for 3.x
>
>         Attachments: jira_files_4_total.zip
>
>
>   At a large company, maven become impossible to use via proxy when maven upgraded from 1.0.10 to 2.1.  maven has always worked fine via proxy in 2.0.9 and continues to work fine.  however maven via proxy always fails in version 2.1.0 and higher.  
>   Attached is a  zip file containing   1) log of GMAIL chat between the creater of this JIRA and a maven developer.  2) two console outputs of running maven 2.2. RC3 showing the proxy failure messages.  3) setting.xml (with comments stripped out)

-- 
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