-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cloudflare blocking endpoint label rendering #10983
Comments
Badge tested using |
I have the same issue today from two different source IPs. |
Hi. As noted in #10981 (comment) and #10982 (comment) I've temporarily blocked most traffic to the endpoint badge. This is intended to be a temporary measure, but I can't completely unblock it until the abusive traffic is under control. |
The majority of legitimate requests to the endpoint badge should now be getting served. I'm not going to disclose the precise details of what we are/aren't blocking at the moment as we are still blocking a lot of unwanted traffic and I don't want to make it public how to circumvent that, but the majority of legitimate requests should now be unblocked. I'm going to close these issues but we will continue to monitor the situation. |
@chris48s FYI that our traffic against https://img.shields.io/badge/License-CC%20BY%204.0-lightgrey.svg is still being blocked. |
Thanks, appreciate the help and support sorting this out! It's working for us at least. |
@shawnalpay there are no firewall blocking rules in place on that route. Only |
Are you experiencing an issue with...
shields.io
🐞 Description
Hello. Everything was working well until recently. Suddenly our custom endpoint badge is not rendering. When I went to check the url, seems like cloudfare is blocking it as per below.
I tried to execute the badge online in your website https://shields.io/badges/endpoint-badge and it gives me this output.
🔗 Link to the badge
https://img.shields.io/endpoint?url=https://gist.githubusercontent.com/daquinteroflex/4702549574741e87deaadba436218ebd/raw/tidy3d_extension.json
💡 Possible Solution
Is there a cloudfare configuration causing this?
The text was updated successfully, but these errors were encountered: