Spec Support for 103 Early Hints and other informational response types
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- clojure
- Domain
- backend-api-design
Research direction
Start by reviewing the Ring spec's treatment of final response statuses and the linked RFC 8297 and MDN material for 103 Early Hints. Compare the proposed capability with Jetty's writeInterim(int status, HttpFields headers) entry point. Done means reaching a decision on whether and how Ring should accommodate informational responses.
Written by the indexing model from the issue text.
Description
Currently, the Ring spec focuses on final response statuses (200–599) and doesn’t explicitly cover informational responses (1xx), such as 103 Early Hints RFC 8297, MDN.
This issue is to open a discussion on how (or whether) the Ring spec should accommodate informational response types, particularly for use cases like Early Hints that can improve performance in certain server setups.
Of all the 1xx status codes, I think only 103 Early Hints is worth considering for standardization in ring.
Jetty has support for this via the CompletableFuture<Void> writeInterim(int status, HttpFields headers) method
- Dominant language
- Clojure
- Stars
- 3.9k
- Forks
- 528
- PR merge metrics
- No merged PRs in 30d
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.
More from ring-clojure/ring
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
ring-clojure/ring#546 ·
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
ring-clojure/ring#544 · 3 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
ring-clojure/ring#542 · 5 comments · 2 reactions ·
-
[ring-jetty-adapter] No control over exceptions thrown when obtaining item from ISeq response body Open
Difficulty 4/5 3-5 days Newbie friendliness 35/100
ring-clojure/ring#531 · 4 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
ring-clojure/ring#530 · 3 comments ·
All issues in ring-clojure/ring
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
-
.Team/Metabot Priority:P3
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
needs triage
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
scalar-labs/scalar-jepsen#222 · 1 comment ·