[
https://issues.apache.org/jira/browse/WAGON-479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15796256#comment-15796256
]
Hudson commented on WAGON-479:
------------------------------
SUCCESS: Integrated in Jenkins build maven-wagon #1330 (See
[https://builds.apache.org/job/maven-wagon/1330/])
[WAGON-479] Preemptive auth with HTTP Provider may fail because (michaelo:
[http://git-wip-us.apache.org/repos/asf/?p=maven-wagon.git&a=commit&h=4074598777fad44a3c34c71c5842b71a03e1da3f])
* (edit)
wagon-providers/wagon-http/src/main/java/org/apache/maven/wagon/providers/http/AbstractHttpClientWagon.java
> Preemptive auth with HTTP Provider may fail because BasicScheme is added as
> completed=true to the AuthCache
> -----------------------------------------------------------------------------------------------------------
>
> Key: WAGON-479
> URL: https://issues.apache.org/jira/browse/WAGON-479
> Project: Maven Wagon
> Issue Type: Bug
> Components: wagon-http
> Affects Versions: 2.11
> Reporter: Michael Osipov
> Assignee: Michael Osipov
> Fix For: 2.12
>
>
> Currently, to prepopulate preemptive authentication for target and proxy,
> {{BasicScheme}} is created and {{processChallenge()}} is called. Then it is
> added to the {{AuthCache}}. This causes two issues:
> 1. The [reference
> documentation|https://hc.apache.org/httpcomponents-client-4.5.x/tutorial/html/authentication.html#d5e717]
> never shows to do so.
> 2. With the Jetty 8 upgrade of all tests several unit tests failed because
> the scheme was set to {{completed=true}} initially and never reacted on
> requested preemptive auth or simply obstained from responding to {{401}} with
> proper credentials altogether.
> This issue has been found during WAGON-474.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
