You're over the rate limit. Serve this file from your own servers. Contact support@github.com if you have questions. You're over the rate limit. Serve this file from your own servers. Contact support@github.com if you have questions.Any roadblocks should be eliminated for VIPs, especially if the consequence is just a few bucks more in bandwidth bills.
If file extensions could be used to determine whether a resource could be used like this, we'd only apply the rate limits to those. Browsers don't care about extensions or event content types though. They'll happily use whatever's at the other end of a URL for <link rel=stylesheet>, <script>, and <img> tags.
As for whitelisting, it's a path we just don't want to go down for raw requests. We do a lot of that for the API and it isn't cheap to maintain.
https://code.google.com/p/browsersec/wiki/Part2#Content_hand... http://mimesniff.spec.whatwg.org/
I'd like to be surprised by that but I'm not.
Also note, it is quite easy to transform github urls back and forth.
For all text files, there is a `blob` portion that comes after the repository name and before the branch. You can change that to `blame`, `commits`, `edit`, or `raw`. When changing it to `raw`, the user is redirected to the `raw.github.com` subdomain. `blob` is the normal view, and `commits` is a history of the file.
Note that using the `edit` version will instantly create a fork in your account for that repo. Resulting in notifications for it, regardless of whether you actually edit it. I guess it's eager forking so that the user doesn't notice this in the foreground. Blech.
You can also change the branch name - it is master in this case - to whatever branch you want. Or commit-sha. Or tag. Almost anything tree-ish will work with Github's UI.
The cool thing about this is that it also pretty much works for the gist service they provide, which allows you to do stuff like:
- create javascript-based inline diffs
- show changes across multiple forks of a gist
- consolidate commits for a file