API user agent

Posts: 7 · Views: 101
  • 40366

    I noticed that my bot was receiving a 403 today when trying to access the wallhaven api. I tried the request via curl on my local machine and got the same result. It worked in the browser, though. So then I tried to add my browsers user agent string as a header in the curl request and it worked again.

    Is this a bug/regression or is this intentional?

  • 40367

    I can confirm, it's not working using CURL or WGET but it's working if url is opened via browser.

    This is definitely a BUG if even using basic curl doesn't work.

    Note: Tested using linux servers, local mac, and local windows.

  • 40369

    Same here.

    It looks like Cloudflare aggressiveness got cranked up (see browser fingerprinting screen before login, I think thats new), and API was not excluded.

  • 40371

    Yeah same problem for my app John's Background Switcher, every API call fails with a 403. Same Cloudflare behaviour as above.

  • 40372

    I hope this can be fixed, as a long time user for John's Background Switcher, this is very important to me (any why I supported the site before, when that was still a thing).

  • 40373

    Should be fixed now, was messing around with our CF config.

  • 40374

    Yay! Can confirm all is well from my app's point of view. Thanks! :)

Message