편집토론기록

사용자:하늘/참고/CDN: 두 판 사이의 차이

< 사용자:하늘
편집 요약 없음
편집 요약 없음
 
(같은 사용자의 중간 판 5개는 보이지 않습니다)
1번째 줄: 1번째 줄:
<includeonly><onlyinclude><div class="youtube" style="{{#switch:{{{4|{{{정렬|}}}}}}
== github => jsdelivr ==
| left|왼쪽 = float: left;
https://stackoverflow.com/questions/17341122/link-and-execute-external-javascript-file-hosted-on-github
| right|오른쪽 = float: right;
| center|가운데 = text-align:center;}}">{{#if:{{{1|}}}|{{#tag:youtube|{{{1|}}}
|width={{{2|{{{너비|}}}}}}
|height={{{3|{{{높이|}}}}}}}}{{#if:{{{5|{{{캡션|}}}}}}|<div align=center><p>{{{5|{{{캡션}}}}}}</p></div>}}</div>{{#if:{{{분류제외|}}}||[[분류:유튜브 영상이 포함된 문서]]}}|<span class="error">링크가 잘못되었습니다.</span>}}</onlyinclude></includeonly>


{{ {{FULLPAGENAME}}|}}
There ''is'' a good workaround for this, now, by using jsdelivr.net.
 
'''Steps''':
 
# Find your link on GitHub, and click to the "Raw" version.
# Copy the URL.
# Change <code>raw.githubusercontent.com</code> to <code>cdn.jsdelivr.net</code>
# Insert <code>/gh/</code> before your username.
# Remove the <code>branch</code> name.
# (Optional) Insert the ''version'' you want to link to, as <code>@version</code> (if you do not do this, you will get the ''latest'' - which may cause long-term caching)
 
----'''Examples''':
<code><nowiki>http://raw.githubusercontent.com/</nowiki><username>/<repo>/<branch>/path/to/file.js</code>
Use this URL to get the latest version:
<code><nowiki>http://cdn.jsdelivr.net/gh/</nowiki><username>/<repo>/path/to/file.js</code>
Use this URL to get a specific version or commit hash:
<code><nowiki>http://cdn.jsdelivr.net/gh/</nowiki><username>/<repo>@<version or hash>/path/to/file.js</code>
'''For production environments''', consider targeting a specific tag or commit-hash rather than the branch. Using the ''latest'' link may result in long-term caching of the file, causing your link to not be updated as you push new versions. Linking to a file by commit-hash or tag makes the link unique to version.
----'''Why is this needed?'''
 
In 2013, GitHub started using <code>X-Content-Type-Options: nosniff</code>, which instructs more modern browsers to enforce strict MIME type checking. It then returns the raw files in a MIME type returned by the server, preventing the browser from using the file as-intended (if the browser honors the setting).

2023년 12월 31일 (일) 01:22 기준 최신판

github => jsdelivr[편집 | 원본 편집]

https://stackoverflow.com/questions/17341122/link-and-execute-external-javascript-file-hosted-on-github

There is a good workaround for this, now, by using jsdelivr.net.

Steps:

  1. Find your link on GitHub, and click to the "Raw" version.
  2. Copy the URL.
  3. Change raw.githubusercontent.com to cdn.jsdelivr.net
  4. Insert /gh/ before your username.
  5. Remove the branch name.
  6. (Optional) Insert the version you want to link to, as @version (if you do not do this, you will get the latest - which may cause long-term caching)

Examples: 

http://raw.githubusercontent.com/<username>/<repo>/<branch>/path/to/file.js

Use this URL to get the latest version: 

http://cdn.jsdelivr.net/gh/<username>/<repo>/path/to/file.js

Use this URL to get a specific version or commit hash: 

http://cdn.jsdelivr.net/gh/<username>/<repo>@<version or hash>/path/to/file.js

For production environments, consider targeting a specific tag or commit-hash rather than the branch. Using the latest link may result in long-term caching of the file, causing your link to not be updated as you push new versions. Linking to a file by commit-hash or tag makes the link unique to version.

Why is this needed?

In 2013, GitHub started using X-Content-Type-Options: nosniff, which instructs more modern browsers to enforce strict MIME type checking. It then returns the raw files in a MIME type returned by the server, preventing the browser from using the file as-intended (if the browser honors the setting).