Fix omdbapi protocol #684
Open
Fix omdbapi protocol #684
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
As per documentation on https://www.omdbapi.com the protocol for the API is HTTP not HTTPS. Even with a correct API key requests against https are returning 401. ``` curl -s -o /dev/null -w "%{http_code}" "https://www.omdbapi.com/?i=tt3896198&apikey=cafecafe" 401 ``` where as ``` curl -s -o /dev/null -w "%{http_code}" "http://www.omdbapi.com/?i=tt3896198&apikey=cafecafe" 200 ```
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
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.
As per documentation on https://www.omdbapi.com the protocol for the API is HTTP not HTTPS.
Even with a correct API key requests against https://... are returning 401.
where as
one could argue that https should work as well, so I emailed the owner of OMDB as well.