Mechanism to automatically verify existence of a fiddle?

[dead-claudia]

We have a broken link checker in our GitHub Actions workflow, and it's returning 403s now. How should we work around it?

I tried a bare request without headers, and that seems to return something.

And to be clear, this is what generated that.

If it's anti-spam (as I suspect), I'd be okay with adding an API token header and/or retargeting it if needed. If that's the case, please tell me how/where I can get that, so we can unbreak our CI.

[oskarkrawczyk]

My bet is CloudFlare detects this request as suspicious and blocks it.

It this being made from a specific host/ip?

[dead-claudia]

@oskarkrawczyk It's from a GitHub-hosted runner, so I don't know.

[dead-claudia]

Okay, appears to probably be a flake caused by triggering anti-bot protections. I tried it with a concurrency-limited requestor and some extra headers, and that seems to work. So, I'm closing this.