Accept status code 429 on com.google.fonts/check/metadata/broken_links
See original GitHub issue429 = "too many requests"
I think this should be considered evidence of a good / live URL, so the check should accept it.
Issue Analytics
- State:
- Created 3 years ago
- Comments:10 (5 by maintainers)
Top Results From Across the Web
What an HTTP Error 429 Means & How to Fix It - HubSpot Blog
HTTP Error 429 is an HTTP response status code that indicates the client application has surpassed its rate limit, or number of requests...
Read more >How to Fix 429 Too Many Requests Error - Kinsta
The 429 status code is intended for use with rate-limiting schemes. Check Out Our Video Guide to the 429 Too Many Requests Error....
Read more >429 Too Many Requests - HTTP - MDN Web Docs
The HTTP 429 Too Many Requests response status code indicates the user has sent too many requests in a given amount of time...
Read more >How to Fix 429 Too Many Requests Error Code - Hostinger
Don't know how to deal with the 429 too many requests error? We'll share the six effective solutions to diagnose and resolve it!...
Read more >429 Error – Too Many Requests HTTP Code Explained
The 429 error is an HTTP status code. It tells you when the use of an internet resource has surpassed the number of...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I’ve double-checked (no pun intended) and both checks run one per family (the metadata one and the description_html one)
I think that’s reasonable.