fetch-booru/fetch_options
2024-03-24 17:05:30 -04:00
..
e621.net.json move fetch options to own directory; only send special user-agent to e621 API 2024-03-24 17:05:30 -04:00
README.md move fetch options to own directory; only send special user-agent to e621 API 2024-03-24 17:05:30 -04:00

fetch_options/[hostname].json

Each request will look for a corresponding fetch_options/[hostname].json and, if present, will use it as the second argument in all fetch calls.

For example, if you have a cf_clearance cookie for the Cloudflare protection in front of a given site, you can create fetch_options/example.com.json

{ "headers": { "cookie": "cf_clearance=whatever", "user-agent": "whatever" } }

and this cookie and user-agent will be used for network calls to example.com. Note that these will not automatically apply to subdomains.