eclipse-ee4j / eclipse-ee4j/jersey
Asynchronous Request Causes Synchronous Repeat for Non-Preemptive 401 Authorization
- Dominant language
- Java
- Stars
- 730
- Forks
- 382
- PR merge metrics
- No merged PRs in 30d
Description
https://github.com/eclipse-ee4j/jersey/blob/360d69d4cbda29dec7c0dee92dbc1b1204090594/core-client/src/main/java/org/glassfish/jersey/client/ClientRuntime.java#L173
Is there a way to propel the asynchronous nature of a request forward so that a HttpAuthenticationFilter, and other filters, can have knowledge about the request and make an asynchronous request instead of a synchronous request in the event that a repeat must be performed, such as with a non-preemptive 401?
Contributor guide
Research direction
Start with core-client/src/main/java/org/glassfish/jersey/client/ClientRuntime.java at the referenced line, then inspect HttpAuthenticationFilter and the other filters involved in request repeats. Determine how an asynchronous request is currently converted to a synchronous repeat for non-preemptive 401 responses. Done means the repeat can remain asynchronous while filters retain the request context needed to initiate it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, authentication
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100