swagger-api / swagger-api/validator-badge
Intermittent 403 Forbidden responses
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 227
- Forks
- 81
- Avg merge
- 2h 3m
- Merged PRs (30d)
- 1
Description
Recently I've started getting intermittent 403 Forbidden responses from https://validator.swagger.io/validator/debug when running on GitHub Actions. (c.f. Job 79811483513):
HTTP/2 403
date: Fri, 05 Jun 2026 20:50:51 GMT
content-type: text/html
content-length: 118
connection: keep-alive
<html>
<head><title>403 Forbidden</title></head>
<body>
<center><h1>403 Forbidden</h1></center>
</body>
</html>
Perhaps this is due to IP-based rate limiting? Do you have recommended guidance for how projects using the validator should handle this scenario? Wait and retry? Don't use the validator from GitHub Actions (or CI pipelines in general)?
Thanks,
Kevin
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing GitHub Actions job 79811483513 and reproducing requests to https://validator.swagger.io/validator/debug. Determine whether the intermittent 403 responses indicate rate limiting or another service-side condition, then define and document appropriate CI guidance such as retrying or avoiding the validator in pipelines.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100