Consider changing URL for Vagrant keys?

[gregelin]

https://raw.github.com/mitchellh/vagrant/master/keys/vagrant.pub redirects to: https://raw.githubusercontent.com/mitchellh/vagrant/master/keys/vagrant.pub

I think the redirect wa failing yesterday and causing my key failure. I received a not found error on the url https://raw.github.com/... this morning.

Redirect seems to be working now:

new-host-2:~ greg$ wget --no-check-certificate https://raw.github.com/mitchellh/vagrant/master/keys/vagrant.pub
--2014-05-30 08:42:07--  https://raw.github.com/mitchellh/vagrant/master/keys/vagrant.pub
Resolving raw.github.com... 23.235.46.133
Connecting to raw.github.com|23.235.46.133|:443... connected.
WARNING: cannot verify raw.github.com's certificate, issued by `/C=US/O=DigiCert Inc/OU=www.digicert.com/CN=DigiCert High Assurance CA-3':
  Unable to locally verify the issuer's authority.
WARNING: certificate common name `www.github.com' doesn't match requested host name `raw.github.com'.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: https://raw.githubusercontent.com/mitchellh/vagrant/master/keys/vagrant.pub [following]
--2014-05-30 08:42:07--  https://raw.githubusercontent.com/mitchellh/vagrant/master/keys/vagrant.pub
Resolving raw.githubusercontent.com... 23.235.46.133
Connecting to raw.githubusercontent.com|23.235.46.133|:443... connected.
WARNING: cannot verify raw.githubusercontent.com's certificate, issued by `/C=US/O=DigiCert Inc/OU=www.digicert.com/CN=DigiCert High Assurance CA-3':
  Unable to locally verify the issuer's authority.
WARNING: certificate common name `www.github.com' doesn't match requested host name `raw.githubusercontent.com'.
HTTP request sent, awaiting response... 200 OK
Length: 409 [text/plain]
Saving to: `vagrant.pub'

100%[=================================================================================================>] 409         --.-K/s   in 0s

2014-05-30 08:42:07 (10.5 MB/s) - `vagrant.pub' saved [409/409]

[wilas]

Base on the following article: https://developer.github.com/changes/2014-04-25-user-content-security/ both links should works, one is just redirect. wget by default (on Linux) follows redirects, so there is not need to change url (if you are not happy with wget, curl -Lk do the job). It's difficult to guest what happen without logs (maybe your minimal setup was missing wget ? maybe there was a problem with your network, maybe the problem with GH ?).

Wget has a few options which may be interested for you:

--output-file=logfile
  Log all messages to logfile...
 --debug
  Turn on debug output...

For more I recommend man wget

Close as impossible to reproduce.