swagger-api / swagger-api/validator-badge
Image served without a content-type header is breaking github's cache
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 227
- Forks
- 81
- Avg merge
- 2h 3m
- Merged PRs (30d)
- 1
Description
You can see the effect of this in the project's own README.
See https://help.github.com/articles/why-do-my-images-have-strange-urls/ for further information.
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 image referenced in the project's README and inspect how the project serves that response. Compare its headers with GitHub's image-cache requirements, then add coverage showing the expected content type and verify the README image still renders correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100