[
https://issues.apache.org/jira/browse/IVY-996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xavier Hanin resolved IVY-996.
------------------------------
Resolution: Fixed
Fix Version/s: trunk
I've made some modifications on trunk which should fix this as you asked:
making head requests only for potential matches. I've made some testing in my
environment, and it works well. I'd appreciate feedback though to know if it
works for you too.
> Remove excessive HEAD requests for URL repository
> -------------------------------------------------
>
> Key: IVY-996
> URL: https://issues.apache.org/jira/browse/IVY-996
> Project: Ivy
> Issue Type: Improvement
> Components: Core
> Affects Versions: 2.0-RC2
> Reporter: Eric Anderson
> Assignee: Xavier Hanin
> Fix For: trunk
>
>
> h3. Fixing useless extra HEAD requests
> When searching for an artifact named "project" version "2.2.+" for
> organization "org", Ivy attempts HEAD requests for completely not possible
> versions.
> IE: /org/project/0.9.2/ivy-0.9.2.xml
> This is not terribly painful unless you have thousands of builds and are not
> on the same network as your ivy server.
> h3. Are HEAD requests even necessary?
> Simply getting a directory listing should be good enough to determine if
> there is an artifact (for choosing latest-release). Now, after one is chosen,
> if no ivy.xml file exists, I could understand trying the next one, but trying
> all of them, just to select the latest one anyways seems like a complete
> waste.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
