2 ms·
This looks like an obvious misconfiguration, after passing the first quick Cloudflare check you should've been forwarded to a page with the right results. Sound
by jeroenhd 3y ago
This looks like an obvious misconfiguration, after passing the first quick Cloudflare check you should've been forwarded to a page with the right results. Sounds like Troy needs to fix his API calls.
Just out of interest, have you checked if installing Cloudflare's Privacy Pass bypasses the issue?
- macNchz 3y agoI’ve encountered this kind of loop on a number of different sites lately, so it may be more than a single misconfiguration. (US residential IP, using Firefox on Linux / Safari on iOS with Private Access Tokens disabled on principle). I’ve just figured it was a fully intentional tarpit, and that I scored too high on some bot heuristic.
- jeroenhd 3y agoIt's possible that the loop is just a tarpit, but based on the contents of the blog post I don't think this is intentional on the website's end. I can think of different ways how this could go wrong (i.e. Cloudflare tries to forward the POST request and CSRF/WAF firewalls block the unexpected Cloudflare origin).