Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.
Sign upMissing charset in content-type HTTP header #43
Closed
Comments
This comment has been minimized.
This comment has been minimized.
|
Aaaaaaannnnnddddd Done: 1e00bfb you'll probably need to clear your browsers cache before you see it go live, but otherwise it should be active now! Let me know if you have any other issues! |
This comment has been minimized.
This comment has been minimized.
|
Looks perfect now. Great job! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I noticed that some JavaScript files look garbled when viewed directly in the browser via a GitCDN URL. Compare for instance
https://rawgit.com/muan/emoji/gh-pages/javascripts/emojilib/index.js (looks OK)
with
https://gitcdn.xyz/repo/muan/emoji/gh-pages/javascripts/emojilib/index.js (garbled)
Apparently GitCDN is not adding
charset=utf-8on content-type headers when serving JS files, and that causes browsers to display those files as if they were ISO-8859-1 encoded. Of course, that's not a problem when the files are loaded in a HTML page, it just looks silly to developers who look at them.I was wondering if there is a way we can get the UTF-8 charset added. Other CDNs I'm aware of (RawGit, raw.githack.com, Staticaly, etc.) do that already.