3 ms·

You're over the rate limit. Serve this file from your own servers. Contact support@github.com if you have questions.

• josegonzalez 14y ago
  You can view the text at this link: https://github.com/git/git/blob/master/Documentation/RelNotes/1.8.0.txt https://github.com/git/git/blob/master/Documentation/RelNote... 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 Pretty hackable.
• ragsagar 14y ago
  https://github.com/git/git/blob/8c7a786b6c8eae8eac91083cdc9a6e337bc133b0/Documentation/RelNotes/1.8.0.txt https://github.com/git/git/blob/8c7a786b6c8eae8eac91083cdc9a...
• reitzensteinm 14y ago
  I'm surprised they don't exempt high profile public projects from limits like that. Git being hosted on Github is hugely beneficial to their image. Any roadblocks should be eliminated for VIPs, especially if the consequence is just a few bucks more in bandwidth bills.
  • rtomayko 14y ago
    We actually don't care about rate limits with this type of raw request. The limits are in place because people (usually porn sites) hot link js/css/image assets which can lead quickly to an insane number of requests. 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.
    • Tobu 14y ago
      Browsers will ignore content-type in many cases (html5 embraced that quirk), but they do have to sniff the bytes to confirm their hunch. You could use `file` to detect images. Or use the content length, maybe by changing hit quotas into bandwidth quotas. https://code.google.com/p/browsersec/wiki/Part2#Content_handling_mechanisms https://code.google.com/p/browsersec/wiki/Part2#Content_hand... http://mimesniff.spec.whatwg.org/ http://mimesniff.spec.whatwg.org/
    • nicholassmith 14y ago
      "The limits are in place because people (usually porn sites) hot link js/css/image assets" I'd like to be surprised by that but I'm not.
• chaitanyav 14y ago
  got the same "You're over the rate limit. Serve this file from your own servers. Contact support@github.com if you have questions."
  • ragsagar 14y ago
    i am able to access the file from that link.