RedSquirrel87 / manga-downloader

A very simple application written in JAVA to download any chapters of any manga from the supported websites
34 stars 1 forks source link

1stkissmanga.io not loading mangas #719

Closed RedSquirrel87 closed 1 year ago

RedSquirrel87 commented 2 years ago

Original report by Pamela Piyavunno (Bitbucket: [Pamela Piyavunno](https://bitbucket.org/Pamela Piyavunno), ).


https://1stkissmanga.io/manga/beauty-and-the-beasts/

*Can’t located jvm_log.txt

Manga Downloader status shows that 1stkissmanga.io is “Working”. However when I attempt to load any manga title from the site it doesn’t load any chapters. Even after attempting to bypass the antibot protection with Manga Downloader assistant or using another browser. Please address this issue, thank you.

RedSquirrel87 commented 2 years ago

Original comment by Red Squirrel (Bitbucket: Red_Squirrel, GitHub: RedSquirrel87).


Just tested, yes it seems that unfortunatly the bypass method for Cloudflare antibot protection (with web browser’s extension) does not work anymore with this website. Fortunately it doesn't seem to be a heavy block because it seems to work simply by adding another cookie currently missing in the requests, I'll try to fix this already in the new upcoming version

RedSquirrel87 commented 2 years ago

Original comment by Pamela Piyavunno (Bitbucket: [Pamela Piyavunno](https://bitbucket.org/Pamela Piyavunno), ).


Thank you!

RedSquirrel87 commented 2 years ago

Original comment by Ryszard Adamus (Bitbucket: [Ryszard Adamus](https://bitbucket.org/Ryszard Adamus), ).


I have been tested some title (not beauty and the beast) and didn’t have much issue with data provided from manga downloader extension. Although, the time I could use the data allowed me to only fetch 3 or 4 episodes, and i had to force cloudflare mechanism but it is understandable for anoyannce like cloudflare to be a bother.

EDIT: i started to wonder, is the issue OP reported somehow the reason why the additional data to bypass CF works only for quite short time and then it is needed to force antibot protection in addon? Because it seems that browser like firefox or chrome can work for much much longer time without proving that user is still not bot.

RedSquirrel87 commented 2 years ago

Original comment by Red Squirrel (Bitbucket: Red_Squirrel, GitHub: RedSquirrel87).


I just tried and yes, it seems they reverted the thing, now it works also without the new cookie. If you still have issues then just delete the cookie.dat file (inside the program’s main folder) and use again the data from the web browser extension

RedSquirrel87 commented 1 year ago

Original comment by Ryszard Adamus (Bitbucket: [Ryszard Adamus](https://bitbucket.org/Ryszard Adamus), ).


I wonder, if I put the data out by extension as a part of python request header will it allow me to pass by CF as well?

RedSquirrel87 commented 1 year ago

Original comment by Red Squirrel (Bitbucket: Red_Squirrel, GitHub: RedSquirrel87).


The data generated from the extension are just the cookies of your web browser (linked to its user-agent) so yeah, they could be used in any type of web request

RedSquirrel87 commented 1 year ago

Original comment by Ryszard Adamus (Bitbucket: [Ryszard Adamus](https://bitbucket.org/Ryszard Adamus), ).


Is there any other hidden mechanism behind CF that browser still works, but data fetched from extension is no longer valid in Manga Downloader, and I need to force recaptcha from extension?

RedSquirrel87 commented 1 year ago

Original comment by Red Squirrel (Bitbucket: Red_Squirrel, GitHub: RedSquirrel87).


That’s because cloudflare bypass cookies have an expiration date for security reasons, so they stop working after a certain period of time and they need to be regenerated by passing cloudflare verification process (and the force button in the web extension only serves to trigger the cloudflare verification process).

RedSquirrel87 commented 1 year ago

Original comment by Red Squirrel (Bitbucket: Red_Squirrel, GitHub: RedSquirrel87).


About the fact that web browsers do not need to force the cloudflare verification process to work, I don't know exactly why, I guess it's due to some internal Cloudflare whitelist. If we knew exactly how it works then we could bypass the protection without even using the web extension xD