HTTPS endpoints #14
Open
HTTPS endpoints #14
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
…on HTTPS with their profile, and this is just a safer fallback
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.
Updated the URLs for the calls to Twitter as the user could be based on HTTPS with their profile, and this is just a safer fallback
Also, if the user is set to use HTTPS and the calls are made on HTTP, it gives a "invalid signature" error back on posts/gets that require a authenticated request. If the user's profile is HTTP and the calls are made to the HTTPS, there is a slight performance impact but doesn't break as in the other case