[
https://issues.apache.org/jira/browse/IVY-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12464147
]
Maarten Coene commented on IVY-380:
-----------------------------------
Maybe we can add an extra attribute to the URL resolver to specify the
Cache-Control behavior?
<url name="my-url-resolver" cache-control="max-age=3600">
...
</url>
> Ivy should force cache refresh on artifact retrieval, to get past caching
> proxies
> ---------------------------------------------------------------------------------
>
> Key: IVY-380
> URL: https://issues.apache.org/jira/browse/IVY-380
> Project: Ivy
> Issue Type: Improvement
> Components: Core
> Affects Versions: 1.4.1
> Reporter: Steve Loughran
> Priority: Minor
>
> I can't resolve stuff
> [ivy:resolve] problem while downloading ivy file:
> http://www.ibiblio.org/maven2/org/apache/ant/ant/1.7.0/ant-1.7.0.pom to
> /tmp/ivy8652xml: invalid sha1
> [ivy:resolve] module not found: [ org.apache.ant | ant | 1.7.0 ]
> The Sha1 was wrong, but it has been fixed now, but the old file is hanging
> around in cache. I have to purge the entries by hand using firefox
> shift-reload.
> If ivy did its gets with a Cache-control header that specified the max age
> for a cached artifact, we wouldnt have this problem. either we should have a
> default "60 minutes" or some way to force it a full refresh.
> see : http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.9
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
