spring-cloud / spring-cloud/spring-cloud-gateway
SecureHeaders filter to run for static content served from gateway
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 4.9k
- Forks
- 3.5k
- Avg merge
- 20h 57m
- Merged PRs (30d)
- 8
Description
If serving static content is a valid use case I'd like to be able to have SecureHeaders filter cover static content.
I tried with it as a default-filter but that only seems to cover matched routes and I couldn't find a way to have a default or catch-all route.
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 tracing how the SecureHeaders filter applies to matched routes and how static content is served through the gateway. Determine whether a default or catch-all route can cover static content, and define completion as SecureHeaders applying consistently to that content without breaking existing route handling.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring, spring-boot
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100