Use HTTPS where we can, and remove hard-coded port 80 #178
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
|
Do all of the providers support HTTPS? Have you tested this? I can test against Testingbot if need be, because I have an account there. @stephendonner |
|
@BeyondEvil thanks; I could clearly use the help, here. Yes, TestingBot's API supports HTTPS, and is used in their API docs' examples: https://testingbot.com/support/api The Python client, though, uses primarily HTTP throughout its docs. |
|
As my previous comment stated, this has now been handled. Thanks for bringing this to us. 👍 |
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.
Sorry for the delay, and the mess. I've taken another clean shot (hopefully) at this.