Ricardo Wurmus <rek...@elephly.net> writes:
>>>> No, upstream needs to fix their invalid Content-Type header. We've
>>>> had this problem a few times, most recently with rubygems.org, and in
>>>> all cases we've gotten upstream to fix it. Strict header parsing can
>>>> seem like an issue at times, but it's really a very good feature that
>>>> the rest of the world seems to ignore. [0]
>>>
>>> I wonder what a correct Content-Type header would look like in this
>>> case. I would like to submit a helpful report containing what I got and
>>> what it should have been.
>>
>> In this case, application/x-gzip or application/octet-stream would be
>> appropriate. Less specifically, the media type needs to match the
>> syntax as defined by the W3C spec. [0]
>
> Thanks, I opened a support ticket with Github.com.
And the response from Github is that it won’t be fixed as this is a
deprecated downloads endpont,
“meaning there wont' be any changes like this made to that.
https://github.com/blog/1302-goodbye-uploads
These endpoints were deprecated on December 12, 2012.”
So, fetching the sources from there won’t work. That’s okay, though, as
we can continue to use the git reference.
~~ Ricardo
