[
https://issues.apache.org/jira/browse/IVY-1280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16348368#comment-16348368
]
ASF GitHub Bot commented on IVY-1280:
-------------------------------------
GitHub user twogee opened a pull request:
https://github.com/apache/ant-ivy/pull/64
IVY-1280 Support preemptive authentication
I adopted a patch by @AurelienLourot
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/twogee/ant-ivy ivy-1280
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ant-ivy/pull/64.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #64
----
commit 2422f51ffad184465a5a9bacdc92e44f7f4a756a
Author: twogee <g.grigelionis@...>
Date: 2018-02-01T10:40:10Z
IVY-1280 Support preemptive authentication
----
> Ivy does not keep track of HTTP session when BASIC authentication is used
> -------------------------------------------------------------------------
>
> Key: IVY-1280
> URL: https://issues.apache.org/jira/browse/IVY-1280
> Project: Ivy
> Issue Type: Improvement
> Components: Core
> Affects Versions: 2.2.0
> Environment: Any
> Reporter: Anders Jacobsson
> Priority: Minor
>
> When publishing through <ant:publish>, each PUT request towards the URL
> resolver (Artifactory, protected with BASIC authentication) seems to be
> duplicated, the first request without any authorization header and the second
> one with. This creates unnecessary network traffic and increases build time.
> Ivy should keep track of any established HTTP session and reuse that one,
> i.e. only the very first request is duplicated.
> I am using Commons HttpClient.
> An alternative would be to expose preemptive authentication so that it is
> configurable. It is less secure but still useful as it would probably mostly
> be used for internal resolvers.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
