Feature Reuqest: Can't find upstream peer, response error
Closed this issue · 3 comments
What is the problem your feature solves, or the need it fulfills?
Maybe can't match host, path or header, response error
Describe the solution you'd like
can custom error response
Describe alternatives you've considered
If upstream peer is empty, call function: 'upstream_error_response' (or other name
@tianxiu2b2t complete explanation and use-case would be much appreciated.
as far as i know, custom responses (either error or early close) is already do able in either of gateway or proxy upstream. for my use cases are like this gateway code and this proxy code . you can write simple function extension to handle that.
there are few other way also to handle it, but that's my implementation.
hope it helps.
This question has been stale for a week. It will be closed in an additional day if not updated.
This issue has been closed because it has been stalled with no activity.