Hello!
On Wed, Oct 28, 2015 at 4:58 PM, 杨阳 wrote:
> for example, a mobile client post some data to nginx, and nginx
> proxy to cache node. For the same url and post data, nginx most time return
> 499 for client close the connections and return 500 for some time which we
> can ensure it have exec header_filter_by_lua step, but how to know in which
> case, nginx return 500 .
>
Many things can trigger 500 and the most reliable way is to check out
the corresponding error log entries. Maybe you just shouldn't try
recording the details in a response header online but rely on offline
error log data analysis.
Regards,
-agentzh