spring-projects / spring-projects/spring-security
addFilterAt exception
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 9.6k
- Forks
- 6.3k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 52
Description
In the following section of the documentation:
https://docs.spring.io/spring-security/reference/servlet/architecture.html
It states:
“Note that if that filter has already been added, then Spring Security will throw an exception.”
However, in practice, adding the same filter type twice to the same SecurityFilterChain using addFilterAt does not always result in an exception.
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
Open the servlet architecture documentation at the linked URL and review the section describing addFilterAt. Compare its statement about adding the same filter type twice with the behavior shown in the report. Done means the documentation accurately reflects when an exception is thrown, or clearly explains the relevant conditions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- documentation, security
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100