Merged
Conversation
Add the ability to catch non-http 200 responses such as 404 and fixed it to make it work. It appears the API Requires cookies (such as a session key) to respond with anything other than a 404. Fixing this was as easy as throwing a GET to the CleverBot homepage while using Requests session handling. Then using this with the POST requests to forward cookies to the API. TD:LR; The API expects specific cookies set by the homepage. Lack of cookies results in a 404
linuxdaemon
pushed a commit
to linuxdaemon/CloudBot
that referenced
this pull request
Oct 10, 2017
Fix last.fm wrapped functions
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
2 participants
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.
Add the ability to catch non-http 200 responses such as 404 and fixed it to make it work.
It appears the API Requires cookies (such as a session key) to respond with anything other than a 404.
Fixing this was as easy as throwing a GET to the CleverBot homepage while using Requests session handling.
Then using this with the POST requests to forward cookies to the API.
TD:LR; The API expects specific cookies set by the homepage. Lack of cookies results in a 404