ring-clojure / ring-clojure/ring
Spec Support for 103 Early Hints and other informational response types
Nobody has claimed this yet.
- Dominant language
- Clojure
- Stars
- 3.9k
- Forks
- 528
- PR merge metrics
- No merged PRs in 30d
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
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 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.
Assessment
- Tech stack
- clojure
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100