The client side of the application does not care about the response from
nginx. It would be acceptable to send a blank
response or send no database at all and simple just close the connection.
After or as the connection is closed I would like the data to work internal
within nginx as normal selecting an upstream proxying it, if the upstream
timeouts or has an error still be able to use nginx_next_upstream.
What would a configuration like this look like ?
If you can (force) close the connection from client side then you can try
proxy_ignore_client_abort setting (
http://nginx.org/en/docs/http/ngx_http_proxy_module.html#proxy_ignore_client_abort
) - which will make nginx to complete the request to upstream.
The other approach (more options to "program" nginx) approach could be to
use something like Echo module ( http://wiki.nginx.org/HttpEchoModule ) from
http://openresty.org/
rr
_______________________________________________
nginx mailing list
[email protected]
http://mailman.nginx.org/mailman/listinfo/nginx
