swagger-api / swagger-api/validator-badge
Can't read from file
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 227
- Forks
- 81
- Avg merge
- 2h 3m
- Merged PRs (30d)
- 1
Description
I am getting the "Can't read from file" error. I see a couple of other related issues, but I am not sure how to further debug this. My specs are available with a quick response time via a direct request from curl or my browser, but the validator can't access them. I have a strong suspicion that it is some setting on Cloudflare that is maybe blocking the validator.
Is there a way to get any more debug information about what the validator sees when it makes the request for my specs? (What HTTP error code does it get, etc?)
Does the validator service make the requests from one or more fixed IP addresses that I can add to my Cloudflare allowlist?
Spec 1:
- https://filterlists.com/api/directory/v1/swagger.json
- https://validator.swagger.io/validator/debug?url=https%3A%2F%2Ffilterlists.com%2Fapi%2Fdirectory%2Fv1%2Fswagger.json
Spec 2:
- https://filterlists.com/api/archival/v1/swagger.json
- https://validator.swagger.io/validator/debug?url=https%3A%2F%2Ffilterlists.com%2Fapi%2Fdirectory%2Fv1%2Fswagger.json
Possibly related:
- #57
- #87
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 with the validator/debug endpoint and reproduce both filterlists.com specification requests, comparing direct browser or curl access with validator access. Review related issues #57 and #87; the work is complete when the validator's HTTP failure details and request source or allowlisting guidance are exposed or clearly documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, openapi
- Domain
- api, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100