Ah, I think I understand the problem you are having now. I think you should try setting both the contentMaxAge and metadataMaxAge to 0. That should ensure that fresh metadata is fetched from the remote on all requests instead of using a cached version. Many formats will tell the client if something exists or not solely based on the metadata and not by trying to download the artifact directly. Assuming that setting works, you will probably want to put some thought into a small, but non-zero age to avoid every request to nexus having to reach out to the remote.
mmartz
(Mmartz)
4
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| Nexus is unable to update the latest NPM dependency package in time | 4 | 6323 | June 16, 2021 | |
| Nexus cache policies | 1 | 5047 | July 17, 2019 | |
| My test Sonatype Nexus Repository Manager OSS 3.24.0-02 is not caching components/artifacts in the proxy repo | 7 | 2423 | October 29, 2020 | |
| Maven repository proxy not caching artifacts? | 0 | 94 | September 4, 2025 | |
| Nexus proxyrepo not syncing with remote hosted-repo | 7 | 13288 | August 20, 2019 |