4 ms·

Not to be the buzz kill, but the reason raw.githubusercontent.com is text/plain and X-Content-Type-Options: nosniff is to keep people from using it as a CDN, be

Not to be the buzz kill, but the reason raw.githubusercontent.com is text/plain and X-Content-Type-Options: nosniff is to keep people from using it as a CDN, because: it's not. The files aren't served static from github: https://github.com/blog/1482-heads-up-nosniff-header-support-coming-to-chrome-and-firefox https://github.com/blog/1482-heads-up-nosniff-header-support... EDIT: I mixed up the move of Pages to .io, updated with the right blog post.

itafroma 13y ago
> Not to be the buzz kill, but the reason raw.githubusercontent.com is text/plain and X-Content-Type-Options: nosniff is to keep people from using it as a CDN, because: it's not. Right, but nothing about this disputes or takes issue with that. The purpose of RawGit is to provide a drop-in replacement URL for use cases where such linking would be desirable from a dev or testing standpoint: it reads the raw version and then serves it statically. There's a CDN option as well: http://rawgit.com/#cdn http://rawgit.com/#cdn