Archiva

404 errors on proxies should be cached

Details

  • Type: Improvement Improvement
  • Status: Closed Closed
  • Priority: Minor Minor
  • Resolution: Fixed
  • Affects Version/s: 1.1
  • Fix Version/s: 1.1
  • Component/s: remote proxy
  • Labels:
    None
  • Number of attachments :
    0

Description

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.

Activity

Hide
Brett Porter added a comment -

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?

Show
Brett Porter added a comment - 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?
Hide
nicolas de loof added a comment -

Yes, we conclude to cache 404. But my first attempt introduced some test failure, so I reverted.

I'll work on this.

Show
nicolas de loof added a comment - Yes, we conclude to cache 404. But my first attempt introduced some test failure, so I reverted. I'll work on this.
Hide
nicolas de loof added a comment -

testcase updated to fetch proxies 2 times.
Depending on cacheFailure enabled / disabled, the wagonMock ensure cahce has been used or not.

Show
nicolas de loof added a comment - testcase updated to fetch proxies 2 times. Depending on cacheFailure enabled / disabled, the wagonMock ensure cahce has been used or not.

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: