This repository was archived by the owner on Aug 6, 2021. It is now read-only.
Use raw.githack for serving response information for asset images - #89
Open
sambacha wants to merge 2 commits into
Open
Use raw.githack for serving response information for asset images#89sambacha wants to merge 2 commits into
sambacha wants to merge 2 commits into
Conversation
added 2 commits
February 3, 2021 23:50
changes the url addressing to use raw.githack which properly appends the correct content type headers and proides cloudflare caching
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This changes the URL addressing to use raw.githack instead of serving them via github.
raw.githack.com acts as a caching proxy, forwarding requests to the corresponding service, caching the responses either for a short time (in the case of development URLs) or permanently (in the case of CDN URLs), and relaying them to your browser with the correct
Content-Typeheaders.