Add status code 308
- Dominant language
- Java
- Stars
- 400
- Forks
- 143
- PR merge metrics
- No merged PRs in 30d
Description
[RFC 7538](https://tools.ietf.org/html/rfc7538) describes the behavior of the HTTP status code **308**. While this RFC is quite new it solves an actual problem regarding POST redirections.
And it completes quite well the **307** status code found in the [HTTP 1.1 RFC](https://tools.ietf.org/html/rfc7231) (previously described in the obsolete [RFC 2616](https://tools.ietf.org/html/rfc2616)).
Contributor guide
Research direction
Start by locating how the existing 307 HTTP status code is defined and exposed, then compare its behavior with RFC 7538 and the HTTP 1.1 specification cited in the issue. Done means status code 308 is supported consistently with 307 and its POST-redirection behavior is covered where the project handles status codes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100