[Support-mirrors] HTTP 300 error on newer Gems

Dennis Oelkers dennis at lauschmusik.de
Tue Nov 22 12:48:15 EST 2005


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hey folks,

Am 22.11.2005 um 17:57 schrieb Tom Copeland:

> Hi all -
>
> It seems like new gems aren't being pushed to Austin's server...  
> when I
> do a "gem install gruff" against halostatue I get an HTTP 300.  Maybe
> I'm redirecting to the wrong directory?  I'm redirecting Gem  
> requests to
> rubyforge.halostatue.info/gems/, Austin, is that the directory that's
> getting sync'd?
>
> Also, shouldn't this just return an HTTP 404 since the gem's not  
> there?
> Or maybe you don't have direct control over that, Austin?
>
> http://rubyforge.halostatue.info/gems/gruff-0.0.5.gem
>

Uhm, the problem is on my side, the script I used to trigger the sync
of the other mirrors was flaky, I am gonna fix it asap.

Austin's host returns a 300, because it (mod_speling?) presents an  
option
for other choices if it does not find the object specified.

Btw, Tom, we should talk about setting up the mechanism which pushes the
updates from your host to mine soon.

Kind regards,
	Dennis Oelkers
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Darwin)

iD8DBQFDg1nkcT9mJF158yMRAsI1AJ9JzEDvWhx8/mUO5E4MKxUrFedw+ACgltmZ
HO0pklmwb7dWRfO4D4V24pc=
=wvKl
-----END PGP SIGNATURE-----


More information about the Support-mirrors mailing list