holysoles / holysoles/facetime
Set Retry-After in 503 responses
Open
- Dominant language
- Go
- Stars
- 2
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
to comply with rfc 9110, a retry-after header should be returned in the 503 response so the client can retry when the server is available again.
Contributor guide
No contributing guide indexed for this repository
Research direction
Inspect the Go webserver's 503 response path and the Gin-related request handlers identified by the repository topics. Confirm how 503 responses are produced, then verify the Retry-After header against RFC 9110 and exercise the relevant response behavior; done means compliant 503 responses include the header.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100