The corporate overlords here recently started blocking the official
Maven repo, so Archiva was getting 403 Forbidden when it tried to hit
the repo. I changed the proxy to one that works now, but Archiva refuses
to forget that it has got a 403 last time it touched central.

How can I get it to hit the repo and realize that it is OK to use the
new proxy now?

Reply via email to