[
https://jira.codehaus.org/browse/WAGON-405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=340227#comment-340227
]
Konrad Windszus commented on WAGON-405:
---------------------------------------
The documentation about the default behaviour was updated at [1]. Thanks a lot
for that. But the example at [2] still does not work for Maven 3.0.4+. Could
someone with write access to that page add the example from the comment above
and add a hint, that this will enable preemptive authentication for GET as
well. Maybe there could be some more information added to [3] about the
different configuration options for the HTTP wagon provider?
[1] - http://maven.apache.org/guides/mini/guide-http-settings.html#Maven_3.0.4
[2] -
http://maven.apache.org/guides/mini/guide-http-settings.html#Example:_Using_Preemptive_Authentication
[3] - http://maven.apache.org/wagon/wagon-providers/wagon-http/
> Preemptive authentication still not working with Maven 3.0.4+
> -------------------------------------------------------------
>
> Key: WAGON-405
> URL: https://jira.codehaus.org/browse/WAGON-405
> Project: Maven Wagon
> Issue Type: Bug
> Reporter: Konrad Windszus
> Attachments: WAGON-405-MVN3.1.1.log
>
>
> Although by default the preemptive authentication should work now with Maven
> 3.0.4, a wireshare dump exposes, that each request for downloading a new
> dependency does not initially come with the authentication header. Only after
> Nexus replied with a 401 the right credentials are set in the authentication
> header. According to [1], since Maven 3.0.4 the default HTTP wagon uses
> preemptive authentication which cannot be disabled [2]. Even with Maven 3.1.1
> it does not work.
> [1] - http://maven.apache.org/guides/mini/guide-http-settings.html#Maven_3.0.4
> [2] -
> http://maven.40175.n5.nabble.com/Maven-3-0-4-preemptive-auth-problem-tt5470892.html#none
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
