-
-
Notifications
You must be signed in to change notification settings - Fork 18
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
About update #34
Comments
Yes soon! I plan to fix it within the next weeks :) Atm I'm very busy with other internal projects. |
Awesome man, looking forward to it. |
Some time ago, about two months ago, it works perfect in a website (protected by cloudflare), but now days it's not working, i hope a update that fix it soon, this is a amazing tool, congratulations! |
ye, looking around of node libraries to bypass these stupid cloudflare screens. Hopefully the creator picks back up the project soon :) |
U will still offer updates for this lib? im checking and can't bypass v1 challenge (iuam) |
I’m really very sorry for not updating as promised. I got really busy with big private projects that I cannot make any time for working on my active open-source projects. |
By reading the code and testing the body response, the new version never gets inside the 503 status code statement (hooman.js file, line: 56 - response.body.includes('var s') ), it doesn't find a 'var s' in the body. Also inside core.js which solves the challenge, it's looking for a 'var s' in the script string... I'm new with this cloudflare stuff, but this is not making sense to me, is the body response different than before? anyways... the library is amazing, never seen something like this before. |
What would you like to discuss?
Checklist
The text was updated successfully, but these errors were encountered: