[
http://jira.codehaus.org/browse/MRM-678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_121835
]
Brett Porter commented on MRM-678:
----------------------------------
didn't we go back and forward on this on the list? I thought the conclusion was
to cache 404's... but if not, was there a counterpoint given as to why not?
> 404 errors on proxies should be cached
> --------------------------------------
>
> Key: MRM-678
> URL: http://jira.codehaus.org/browse/MRM-678
> Project: Archiva
> Issue Type: Improvement
> Components: remote proxy
> Affects Versions: 1.1
> Reporter: nicolas de loof
> Priority: Minor
>
> Using maven eclipse plugin with DownloadSources=true creates lot's of request
> to the repository for -sources and -javadocs. Many artifacts don't have such
> bundles.
> When archiva is configured with multiple proxies (central + java.net + jboss
> ...) a single running "mvn eclipse:eclipse" will result in many 404 request
> on proxies that SHOULD be cached. The cache time-to-live (30 minute) is
> sufficient to get new artifacts when they get deployed.
> There is allready an UrlFailureCache but is only used to cache
> ProxyExceptions.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
