Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

nodeload.github.com vs github.com #1285

Closed
mastacheata opened this issue Nov 5, 2012 · 1 comment
Closed

nodeload.github.com vs github.com #1285

mastacheata opened this issue Nov 5, 2012 · 1 comment

Comments

@mastacheata
Copy link

@mastacheata mastacheata commented Nov 5, 2012

Not sure if this is a change on github, but currently I get only 404s whith composer trying to download zipballs from nodeload.github.com.
I even get these 404 errors when I manually try downloading from nodeload, but it works fine when I choose the same url without the nodeload subdomain.

I can confirm this issue from 2 different computers in different networks at different locations.

I couldn't find any announcements regarding that, but all the links on the github website to zipballs/tarballs also refer to github.com///zipball/ and not to nodeload.github.com

If anyone could provide information that this is the new default behavior of github.com, this should also be changed in composer.

The status page of Github doesn't acknowledge this as a problem (yet?).

EDIT: One more thing: The github.com///zipball/ urls redirect to nodeload.github.com///legacy.zip/
Which hints that this might indeed be a permanent change on github.

@Seldaek

This comment has been minimized.

Copy link
Member

@Seldaek Seldaek commented Nov 6, 2012

I fixed this problem already, try running composer self-update to get the latest version of the phar which should work better.

And indeed, they changed the URLs without notice since nobody is supposed to use nodeload directly, but we do when users don't have the php openssl extension enabled, because the github.com domain is only accessible over SSL.

@Seldaek Seldaek closed this Nov 6, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.