This repository was archived by the owner on Nov 6, 2023. It is now read-only.
Repository navigation
Fix the rule that breaks fotki.com - #1516
Merged
Merged
Conversation
added 2 commits
April 19, 2015 18:47
reedy
added a commit
that referenced
this pull request
Apr 30, 2015
Fix the rule that breaks fotki.com
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.
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.
fotki.com looks completely broken currently with HTTPS Everywhere.
That's because the current rule redirects all static files to cachefly and Fotki does not use cachefly anymore.
Since the rule was created, Fotki added support for https for most of subdomains and it's being constantly improved. So it's better to have a full redirect. (Tested, it seems to work).