Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We are using nginx as a proxy for a Rails app, which processes callback requests. Some of these requests get sent to us in a "fire-and-forget" manner. Meaning, the client closes the connection, immediately after sending the request, without waiting for the response. Nginx cancels the request, logs a 499 and nothing gets through to the Rails app.

Can nginx be configured, so that it still relays the request to the Rails app, even when the client closes the connection, after it has been sent?

share|improve this question
up vote 3 down vote accepted

I was able to fix it with the proxy_ignore_client_abort parameter in the nginx config.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.