Question

我想实现一个功能。

当HTTP请求返回502状态代码时，Nginx返回“ 502 Bad GateWay”和requestUrl

如何配置nginx实现此功能，谢谢。

#/usr/local/nginx/lua/auth/404.lua
ngx.say("502 Bad GateWay ")
local request_method = ngx.var.request_method
ngx.say(request_method)
local request_uri = ngx.var.request_uri
ngx.say(request_uri)
#nginx.conf
 proxy_intercept_errors on ;
 error_page 502 /502.html;
 location =/502.html {
      content_by_lua_file "/usr/local/nginx/lua/auth/404.lua";
 }

Answer 1

您需要proxy_intercept_errors指令。
该伪指令的默认值为off。如果要拦截状态代码大于/等于300（当然包括502）的代理服务器的响应，则必须将其设置为on。 More details about this directive。

这是我测试过的示例配置文件。

upstream tomcat502 {
  server 10.10.100.131:28889; # There is no such a backend server, so it would return 502
}

server {
  listen       10019; # it's up to you
  server_name  10.10.100.133;

  location /intercept502 {
    proxy_intercept_errors on;  # the most important directive, make it on;
    proxy_pass  http://tomcat502/;
    error_page  502 = @502; # redefine 502 error page
  }

  location @502 {
    return 502 $request_uri\n;  # you could return anything you want.
  }
}

重新加载nginx之后，使用curl对其进行测试。

[root@test133 lunatic]# curl http://10.10.100.133:10019/intercept502
/intercept502 
[root@test133 lunatic]# curl http://10.10.100.133:10019/intercept502 -I
HTTP/1.1 502 Bad Gateway
Server: nginx/1.12.1
Date: Wed, 09 Jan 2019 13:48:05 GMT
Content-Type: application/octet-stream
Content-Length: 14
Connection: keep-alive

我在配置中添加了一些解释。希望对您有所帮助。

当HTTP请求返回502状态代码时，Nginx返回“ 502 Bad GateWay” + requestUrl

1 个答案: