adding flags for compatibility w/ full https websites #21
Conversation
This file contains 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
Urigo
added a commit
that referenced
this pull request
Nov 30, 2014
adding flags for compatibility w/ full https websites
|
@diogoriba Great! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
When using angular-embedly on an https-enabled website, there are errors when trying to make the calls to http://embed.ly through an unsecured connection. I'm adding some flags to handle that.
For using it, one should be able to do
embedlyServiceProvider.secure(true);
to their configuration.
I left it turned off by default not to affect the current standard behavior.
Please let me know if I used the correct styling.
Hope this helps!