-
Notifications
You must be signed in to change notification settings - Fork 32
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
if error is from cloudflare, allow to retry manualy #668
Comments
I suggest to implement a retry download for any kind of failure, not just CloudFlare. |
This is rising many questions. Suppose i want to retry downloading a chapter. Should i redo FetchPages then FetchImages? Just FetchImages ? If we need a temporary token to download images that is set in FetchPages and we only retry "fetchImages"? Or we may have two type of retries for "downloading a chapter": Full & partial. Full invalidate "pages cache" and recall FetchPages first while partial will only retry downloading pages. On the other hands, is there ever a need for partial in that case? What should prevent us to always recall FetchPages? |
Under the hood a failed download task will be replaced by a completely new download task, similar to when a user presses the remove button and then the download chapter button again. |
In case the problem is CloudFlare , you will have to go through Hakuneko Assistant to get the cookie and pass the captcha, or you will have to activate your VPN to bypass CloudFlare Geoblocking , I see no point retrying automatically "Cloudflared" requests. The download tasks thingies you mentioned will be fine imho. |
In this issue I juste Ask to a buttons no automation :-) For automatique retry, the only things I see is to support tools like flaresolver that bypass cloudflare check, but it's an other issue |
I try to download from reaperscan that is protected by cloudflare.
Token expire before the end of downloading so a lot of chapter was failed. I update with the assistant but I can not ask to retry all failed with only one button
Can you add this button ?
The text was updated successfully, but these errors were encountered: