OpenConext / OpenConext/OpenConext-oidcng
discussion: HEAD and OPTIONS
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 4
- Forks
- 6
- Avg merge
- 5d 32m
- Merged PRs (30d)
- 3
Description
This issue is imported from pivotal - Originaly created at Mar 11, 2021 by Bart Geesink
We currently set a session when a HEAD or OPTIONS request comes in. This can lead to session errors.
What to do here?
- Block these requests: Might this break some implementations?
- Surpress session errors for sessions created by the methods
- Do not create a session for these requests
Contributor guide
No contributing guide indexed for this repository
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 HEAD and OPTIONS requests are handled and where sessions are created or produce errors. Compare the three proposed behaviors—blocking the requests, suppressing errors, or avoiding session creation—and determine which preserves expected implementations. Done means the project has a decided behavior and corresponding validation for these request methods.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- authentication
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100