Bug 236939

Description David Williams 2008-06-12 13:45:34 EDT

As most know ... there are some cases where if a request for a jar or zip comes in from certain IP addresses, then those requests getting automatically re-directed to a mirror site from which those IP addresses should pull from (such as "fullmoon") instead of directly from Eclipse. 

Occasionally this breaks down when the local (fullmoon) mirror doesn't have the jar (usually due to server breakdowns, sometimes just due to exact timing of replication). 

Most of the time, these "break downs" are not fatal, since if the request for a jar or zip fails, the user knows how to "get around it" using a different mirror (or other tricks). 

But, there is one (two?) new cases, where these "break downs" become fatal. 
With the new P2 software updates, Eclipse code will try to get
http://download.eclipse.org/releases/ganymede/staging/content.jar
But, if that get's redirected to 
<fullmoon>/releases/ganymede/staging/content.jar
and that fullmoon get fails, then Eclipse is hosed, and the user is stuck .. there's no way for them to "override" where to get that initial jar from. 

This is especially troublesome, since the content.jar file is what contains the mirror URL, to tell eclipse from that point on how to compute which mirrors to try. 

I suspect there is a similar sensitivity to 'artifacts.jar'. 
And, of course, these two can be in /releases/ganymede as well as releases/ganymede/staging. 

So, is there anyway to disable the automatic re-direct just for these two jar files?