-
-
Notifications
You must be signed in to change notification settings - Fork 941
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
[Danbooru] Cloudflare challenge warning + 403 error #3665
Comments
https://danbooru.donmai.us/forum_topics/22822 Try using a different |
It worked. I assume that I should just use the user agent extractor option to make Danbooru downloads do this automatically from now on? |
Maybe user-agent should be randomized by default? |
The issue seems to be with the CF browser integrity check or so. Using modern browsers with unmatching system UA will result in 403. However, ancient UAs (e.g., ones from IE6) seem to work without any issues... |
how do you do that please? i wish to make it automatic since i have mutiple links from many platforms and singeling out danbooru is gonna take me a long time |
It's in the list of configuration options here. Just add this line to the Danbooru extractor:
Make sure you add a comma at the end if it's not the only/final option within the extractor. |
Need to remember that some Danbooru sites, such as e621/e962 (although it's a heavily modified codebase), may have limits on user agents. Case in point:
In such cases the appropriate extractor needs to either forcibly override the user-defined one or limit the allowed ones. I vote for the former cuz coming up with the specifications doesn't sound like worth it. |
this removes the ability to set a custom UA via 'user-agent' option for extractor requests
gallery-dl now automatically sends
e621 always automatically sent |
Despite using the username and API key, trying to download from Danbooru - or even attempt to fetch the list of keywords applicable to the site - runs into a Cloudflare challenge warning that's followed with a 403 error.
Here's the verbose log.
The text was updated successfully, but these errors were encountered: