Transparent redirection from download.eclipse.org to archive.eclipse.org in unstable and quickly leads to 503 errors
Summary
It's quite common that projects move content from download.eclipse.org to the same path on archive.eclipse.org. For example
https://download.eclipse.org/modeling/emf/cdo/drops/R20130918-0029
In the browser this yields
The p2 infrastructure generally follows the redirects and works fine:
This appears to have stopped working well after December 18th.
Steps to reproduce
I'm not sure how to reproduce it outside of p2.
A URL like this fails:
If I keep trying to download it in a browser, eventually I see:
That's likely the failure p2 is seeing.
What is the current bug behavior?
In the debugger I see the server is yielding a 503 not a redirect:
What is the expected correct behavior?
I think it should produce a 403 that p2 can and will follow.
Relevant logs and/or screenshots
See above.
Priority
-
Urgent -
High -
Medium -
Low
Severity
-
Blocker -
Major -
Normal -
Low
Impact
You'd be surprised how many tests rely on old locations. I don't know the user impact, we've all relied on being able to move content from download.eclipse.org to archive.eclipse.org