5 ms·
uhm, I'm suddenly completed locked out? Can't even get to the homepage in private browse anymore so must be IP level. Just says "Forbidden". Must have tripped
by Havoc 5mo ago
uhm, I'm suddenly completed locked out?
Can't even get to the homepage in private browse anymore so must be IP level. Just says "Forbidden".
Must have tripped some sort of safeguard while trying to figure out how to use the API via curl
- Havoc 5mo agoOK this is a bit ridiculous. The FAQ does not specify how to use the API beyond listing a json parameter. If you send a curl command with that parameter the first search just returns "Logged In", and run another search and then you're temporarily IP banned site wide. Having hair trigger sensitive security around API while not telling the user what the request should look like to not trigger that is just silly.
- Havoc 5mo agoOK bit more trial and error later I worked out a curl command that doesn't trip this. https://pastebin.com/BNRBfYFf https://pastebin.com/BNRBfYFf Still not entirely sure what about the original request trigger it. Think it was something around the Sec-Fetch-* headers that copying a request from browser via copy cURL included
- BrunoBernardino 5mo agoSorry! You can use the incognito token (from the incognito URL) in order to not have to send the cookie over. If you were trying too aggressively to search, you could've been rate-limited for a few minutes.
- Havoc 5mo agoGood to know about the incognito toke - helpful. Yes, I saw the 3 auth try mentioned in the faq after this, that must have been what I was hitting with the experimenting. Anyway all good now