Using https speech-to-text api instead of http#135
Open
BingLingGroup wants to merge 1 commit intoagermanidis:masterfrom
Open
Using https speech-to-text api instead of http#135BingLingGroup wants to merge 1 commit intoagermanidis:masterfrom
BingLingGroup wants to merge 1 commit intoagermanidis:masterfrom
Conversation
BingLingGroup
force-pushed
the
https-patch
branch
from
4c0fffc to
a60ec3e
Compare
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
1 participant
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.
According to this repo google-speech-v2 and my test, it is ok to change the api url into the https' one. There's no influence on the recognition result. And https is safer than http.
And I also add a fall back argument to choose http or https version url to use.