Issue description
There was a discussion earlier about How to distinguish the source of these response status codes :
Issue 2501 and PR 2817.
The conclusion is that: In the response header of the request, through the response header of X-APISIX-Upstream-Status, we can effectively identify the source of the 5xx status code.
About this, I have a question: Why only distinguish 5xx status codes?
In some scenarios, the requirement may be how to distinguish the source of status codes 4xx.
In addition to this, We can rewrite the upstream status codes by APISIX's response-rewrite plugin. In this case, if we can't distinguish the source of the status code，upstream or apisix，it can’t quickly help us determine the problem.
Therefore, I would like to ask for some opinions of the community：
Distinguish the source (upstream or apisix) of the status code, whether it can be extended to all the status code，not only 5xx.
Issue description
There was a discussion earlier about
How to distinguish the source of these response status codes:Issue 2501 and PR 2817.
The conclusion is that: In the response header of the request, through the response header of
X-APISIX-Upstream-Status, we can effectively identify the source of the5xxstatus code.About this, I have a question:
Why only distinguish 5xx status codes?In some scenarios, the requirement may be how to distinguish the source of status codes 4xx.
In addition to this, We can rewrite the upstream status codes by APISIX's response-rewrite plugin. In this case, if we can't distinguish the source of the status code，upstream or apisix，it can’t quickly help us determine the problem.
Therefore, I would like to ask for some opinions of the community：
Distinguish the source (upstream or apisix) of the status code, whether it can be extended to all the status code，not only 5xx.