Limits of proxy_ignore_client_abort: can nginx finish upstream work after the client disconnects?
I'm designing an nginx reverse proxy in front of a slow upstream that performs long, idempotent processing (report generation). Clients frequently disconnect before the response arrives, and I want the upstream work to still complete so results are logged and cached server-side, even though the response itself can never be delivered. My reading of the ngx_ht
nginx