>>> 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. ~~ Ricardo
