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.
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.