Why does Yarp return 502 status code when a client disconnects?
Open
- Dominant language
- C#
- Stars
- 9.6k
- Forks
- 933
- Avg merge
- 12d 18h
- Merged PRs (30d)
- 2
Description
502 (Bad Gateway) is usually returned when the reverse proxy encounters an error while trying to forward the request to the backend server, but in the case where a client disconnects should it not set the status code to 499?
Contributor guide
Assessment
This issue has not been assessed yet.