starter-security: Investigate changes in Location Header
Open
Nobody has claimed this yet.
help wanted
- Dominant language
- Java
- Stars
- 469
- Forks
- 128
- Avg merge
- 1d 42m
- Merged PRs (30d)
- 156
Description
During the Spring Boot 4 upgrade, changes had to be made to OperatonBpmSecurityAutoConfigOauth2ApplicationIT#testWebappWithUnauthorizedUser
- Previously the location header was absolute.
- With SB4, it os relative.
Investigate why this is, any if it might be a problem.
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 named integration test, OperatonBpmSecurityAutoConfigOauth2ApplicationIT#testWebappWithUnauthorizedUser, and inspect the Location header behavior before and after the Spring Boot 4 upgrade. Determine why the header is now relative, whether that affects the unauthorized response, and record the conclusion or required follow-up.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring-boot
- Domain
- security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100