modified setup-headers to cdn urls, fixes bad header issue #40#46
Open
pigeonflight wants to merge 1 commit into
Open
modified setup-headers to cdn urls, fixes bad header issue #40#46pigeonflight wants to merge 1 commit into
pigeonflight wants to merge 1 commit into
Conversation
|
So to explain this to those simpler souls, like me: sudo vi /etc/apt/sources.list.d/crouton-packages.list Then replace raw.githubusercontent.com with cdn.rawgit.com Thanks for the solution though. Hope my step-by-step explanation helps someone. |
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
On some distros (Ubuntu Trusty and Debian Jessie) using apt-transport-https fails due to additional headers added by github. The solution is to serve the packages via a CDN. In this case I make use of http://rawgit.com
I've modified the repo sources to use cdn.rawgit.com, specifically the http:// version as I was getting certificate errors with the https:// version