Proper Server Response Header Support
- Dominant language
- Rust
- Stars
- 166
- Forks
- 49
- PR merge metrics
- No merged PRs in 30d
Description
There are many [HTTP response headers](https://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.6) that we should be sending back to the client. Here is a list of headers that we may want to support for every single HTTP request. Note, this list may be incomplete and new ones should be added when discovered or removed when deemed not necessary.
* [x] Content-Type
* [x] Date
* [ ] Connection
Contributor guide
Research direction
No source file or test is named in the issue. Start by locating the HTTP response construction and current Content-Type and Date header handling, then review the linked RFC section for the proposed Connection header; done means the intended header behavior is applied consistently to HTTP responses and the checklist requirement is resolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend-api-design, networking
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100