incubator-ivy-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gilles Scokart (JIRA)" <j...@apache.org>
Subject [jira] Commented: (IVY-380) Ivy should force cache refresh on artifact retrieval, to get past caching proxies
Date Wed, 10 Jan 2007 09:30:27 GMT

    [ https://issues.apache.org/jira/browse/IVY-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12463506
] 

Gilles Scokart commented on IVY-380:
------------------------------------

Xavier, I think the problem of Steve is not related to the ivy cache, but to its proxy cache.
 Even if he clean his local ivy cache, its proxy still keep the ibiblio files in cache.

Personally, I don't really like to have the client asking the proxy to systematically not
trust the expiration mechanism asked by the server.

I'm wondering if it is not possible to identify only a limited case where this is required.
 For example, when using changing revisions, and if we ivy would have a clean-cache task (see
IVY-321), after a clean asked explicetly by the user.

> 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

        

Mime
View raw message