You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Erwan Ducroquet (JIRA)" <ji...@codehaus.org> on 2010/11/15 11:44:03 UTC
[jira] Created: (MDEPLOY-125) Do not wait for 401 "authentication
needed" response to send the login/pwd on PUT queries
Do not wait for 401 "authentication needed" response to send the login/pwd on PUT queries
-----------------------------------------------------------------------------------------
Key: MDEPLOY-125
URL: http://jira.codehaus.org/browse/MDEPLOY-125
Project: Maven 2.x Deploy Plugin
Issue Type: Improvement
Components: deploy:deploy
Affects Versions: 2.5
Reporter: Erwan Ducroquet
When the maven repository requires authentication to PUT jars,
1- the deploy plugin first triggers a HTTP PUT query without login/pwd, trying to send the jar
2- then the repo rejects this query as 401 "need authentication" error
3- then the deploy plugin triggers again same HTTP PUT query with the login/pwd and sends the jar again
4- then the repo accepts this second query and uploads the jar
This sequence consumes useless I/O (trying to send the jar on first query)
and causes issues on some configurations like HTTPS with a frontend webserver : randomly the HTTPS connection is cut (Nginx HTTPS forwarding to Nexus HTTPS).
It will be better (by default or with some config var) to provide immediately the login/pwd on PUT queries
=> aka: sending the HTTP header "Authentication: BASIC xxxxx"
Tested with Maven 2.2.1, Deploy 2.5, Nexus 1.7.2, Nginx
--
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
[jira] Moved: (WAGON-317) Do not wait for 401 "authentication
needed" response to send the login/pwd on PUT queries
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/WAGON-317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Bentmann moved MDEPLOY-125 to WAGON-317:
-------------------------------------------------
Component/s: (was: deploy:deploy)
wagon-http-lightweight
Affects Version/s: (was: 2.5)
1.0-beta-6
Key: WAGON-317 (was: MDEPLOY-125)
Project: Maven Wagon (was: Maven 2.x Deploy Plugin)
> Do not wait for 401 "authentication needed" response to send the login/pwd on PUT queries
> -----------------------------------------------------------------------------------------
>
> Key: WAGON-317
> URL: http://jira.codehaus.org/browse/WAGON-317
> Project: Maven Wagon
> Issue Type: Improvement
> Components: wagon-http-lightweight
> Affects Versions: 1.0-beta-6
> Reporter: Erwan Ducroquet
>
> When the maven repository requires authentication to PUT jars,
> 1- the deploy plugin first triggers a HTTP PUT query without login/pwd, trying to send the jar
> 2- then the repo rejects this query as 401 "need authentication" error
> 3- then the deploy plugin triggers again same HTTP PUT query with the login/pwd and sends the jar again
> 4- then the repo accepts this second query and uploads the jar
> This sequence consumes useless I/O (trying to send the jar on first query)
> and causes issues on some configurations like HTTPS with a frontend webserver : randomly the HTTPS connection is cut (Nginx HTTPS forwarding to Nexus HTTPS).
> It will be better (by default or with some config var) to provide immediately the login/pwd on PUT queries
> => aka: sending the HTTP header "Authentication: BASIC xxxxx"
> Tested with Maven 2.2.1, Deploy 2.5, Nexus 1.7.2, Nginx
--
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
[jira] Commented: (WAGON-317) Do not wait for 401 "authentication
needed" response to send the login/pwd on PUT queries
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/WAGON-317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=243127#action_243127 ]
Benjamin Bentmann commented on WAGON-317:
-----------------------------------------
See also [Advanced Configuration of the HttpClient HTTP Wagon|http://maven.apache.org/guides/mini/guide-http-settings.html].
> Do not wait for 401 "authentication needed" response to send the login/pwd on PUT queries
> -----------------------------------------------------------------------------------------
>
> Key: WAGON-317
> URL: http://jira.codehaus.org/browse/WAGON-317
> Project: Maven Wagon
> Issue Type: Improvement
> Components: wagon-http-lightweight
> Affects Versions: 1.0-beta-6
> Reporter: Erwan Ducroquet
>
> When the maven repository requires authentication to PUT jars,
> 1- the deploy plugin first triggers a HTTP PUT query without login/pwd, trying to send the jar
> 2- then the repo rejects this query as 401 "need authentication" error
> 3- then the deploy plugin triggers again same HTTP PUT query with the login/pwd and sends the jar again
> 4- then the repo accepts this second query and uploads the jar
> This sequence consumes useless I/O (trying to send the jar on first query)
> and causes issues on some configurations like HTTPS with a frontend webserver : randomly the HTTPS connection is cut (Nginx HTTPS forwarding to Nexus HTTPS).
> It will be better (by default or with some config var) to provide immediately the login/pwd on PUT queries
> => aka: sending the HTTP header "Authentication: BASIC xxxxx"
> Tested with Maven 2.2.1, Deploy 2.5, Nexus 1.7.2, Nginx
--
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
[jira] Closed: (WAGON-317) Do not wait for 401 "authentication
needed" response to send the login/pwd on PUT queries
Posted by "Olivier Lamy (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/WAGON-317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Olivier Lamy closed WAGON-317.
------------------------------
Resolution: Fixed
Fix Version/s: 2.0
Assignee: Olivier Lamy
preemptive fixed
> Do not wait for 401 "authentication needed" response to send the login/pwd on PUT queries
> -----------------------------------------------------------------------------------------
>
> Key: WAGON-317
> URL: https://jira.codehaus.org/browse/WAGON-317
> Project: Maven Wagon
> Issue Type: Improvement
> Components: wagon-http-lightweight
> Affects Versions: 1.0-beta-6
> Reporter: Erwan Ducroquet
> Assignee: Olivier Lamy
> Fix For: 2.0
>
>
> When the maven repository requires authentication to PUT jars,
> 1- the deploy plugin first triggers a HTTP PUT query without login/pwd, trying to send the jar
> 2- then the repo rejects this query as 401 "need authentication" error
> 3- then the deploy plugin triggers again same HTTP PUT query with the login/pwd and sends the jar again
> 4- then the repo accepts this second query and uploads the jar
> This sequence consumes useless I/O (trying to send the jar on first query)
> and causes issues on some configurations like HTTPS with a frontend webserver : randomly the HTTPS connection is cut (Nginx HTTPS forwarding to Nexus HTTPS).
> It will be better (by default or with some config var) to provide immediately the login/pwd on PUT queries
> => aka: sending the HTTP header "Authentication: BASIC xxxxx"
> Tested with Maven 2.2.1, Deploy 2.5, Nexus 1.7.2, Nginx
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (WAGON-317) Do not wait for 401 "authentication
needed" response to send the login/pwd on PUT queries
Posted by "Erwan Ducroquet (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/WAGON-317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=243772#action_243772 ]
Erwan Ducroquet commented on WAGON-317:
---------------------------------------
As per comment from Benjamin Bentmann, I've checked on this docs and found following config to setup in settings.xml :
settings/servers/server[@id=x]/configuration/wagonProvider='httpclient'
settings/servers/server[@id=x]/configuration/httpConfiguration/put/params/param[name='http.authentication.preemptive' && value='%b,true']
It can be allowed as we only use https, so no risk to send "not needed" credentials
It is currently being tested
> Do not wait for 401 "authentication needed" response to send the login/pwd on PUT queries
> -----------------------------------------------------------------------------------------
>
> Key: WAGON-317
> URL: http://jira.codehaus.org/browse/WAGON-317
> Project: Maven Wagon
> Issue Type: Improvement
> Components: wagon-http-lightweight
> Affects Versions: 1.0-beta-6
> Reporter: Erwan Ducroquet
>
> When the maven repository requires authentication to PUT jars,
> 1- the deploy plugin first triggers a HTTP PUT query without login/pwd, trying to send the jar
> 2- then the repo rejects this query as 401 "need authentication" error
> 3- then the deploy plugin triggers again same HTTP PUT query with the login/pwd and sends the jar again
> 4- then the repo accepts this second query and uploads the jar
> This sequence consumes useless I/O (trying to send the jar on first query)
> and causes issues on some configurations like HTTPS with a frontend webserver : randomly the HTTPS connection is cut (Nginx HTTPS forwarding to Nexus HTTPS).
> It will be better (by default or with some config var) to provide immediately the login/pwd on PUT queries
> => aka: sending the HTTP header "Authentication: BASIC xxxxx"
> Tested with Maven 2.2.1, Deploy 2.5, Nexus 1.7.2, Nginx
--
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