External repo returns 400: Invalid Request resulting in caching 0 byte artifacts

[jodygarnett]

• What are you trying to do?

We were accidentally caching a maven repository that was no longer functioning:

1. A community had setup a maven repository as a GitHub submodule for developer use
2. They then started using the raw GitHub endpoint (receiving a warning letter from GitHub)
3. We setup a nexus cache of this location to give the community time to manage their artifacts better
4. The original content was removed
5. After the cache contents had timed out, Nexus attempted to "refresh" artifacts that were no longer present resulting in 400: Invalid Request errors.

The resulting errors showed up in nexus as zero byte files; leading to widespread confusion.

• What feature or behavior is this required for?

Stable behaviour if external repository being cached in unavailable.

• How could we solve this issue? (Not knowing is okay!)

If the http 400: Invalid Request response code is encountered, do not cache artifact contents.

• Anything else?

The community ticket is here: https://trac.osgeo.org/osgeo/ticket/2978

[TuningYourCode]

Hi, just wanted to tell your that this repository / issue tracker is for the composer plugin of nexus repository manager. Composer is the package manager for php libraries.

As you mentioned maven repository your issue is definitely in the wrong place :)

[jodygarnett]

lol, okay thanks.