Creating One-way connections or Dont wait for upstream

Server NGINX
1

Hello,

I am working on an application where http ( websocket, or any type of
connection) connections will be one direction for inserting data into a
database and queuing data. 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?

Thank you in advance.

Posted at Nginx Forum:

2

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 (

) - 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 ( GitHub - nginxinc/nginx-wiki: ARCHIVED -- Source for the now archived NGINX Wiki section of https://www.nginx.com · GitHub )
from
http://openresty.org/

rr