-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
All requests are getting 404'd #7
Comments
Same here. And same goes for https://github.com/fojas/cleverbot-node so it is indeed probably because of changes on Cleverbot's end. |
👍 might take a look. |
I've updated the default parameters to match the current request structure. There's also a new XVIS cookie that will need to be set before requests to |
@benmanns I am in absolutely no way saying my solution is right; it was pretty hacky, but feel free to take a look for inspiration/to steal: jalada@7571738 Not submitting a pull request because I also mucked around with gems, headers etc. but the cookie management is the key change. (And it works, so far) |
This probably isn't useful, but I whipped together a selenium test in python that can be used with a headless browser to get a simple call/response to cleverbot. Just a hack until hopefully this api business gets sorted out...
|
As per title, this module has stopped working for me. I presume it is due to changes made on Cleverbot's end.
The text was updated successfully, but these errors were encountered: