nodeload.github.com vs github.com #1285
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 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/
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.