It doesn’t send the response to the client, but it still does all the work of generating the response. I use nginx to proxy_pass to django+gunicorn via unix so

It doesn’t send the response to the client, but it still does all the work of generating the response. I use nginx to proxy_pass to django+gunicorn via unix socket. I sometimes see 499 code responses in my nginx logs which I believe means that nginx received a response from the backend, but can’t send it to the client because the client canceled the request. I admit I haven’t actually tested it directly, but I’ve always assumed the django request/response cycle doesn’t get aborted mid request.