On Wed, May 06, 2009 at 12:49:30PM -0700, Joe Van D. wrote:
# nothing in response body
I earlier tried returning a 200 and it seemed to hang on me. Maybe browser
No, returning 200 won’t do anything good. For now it will
basically instruct nginx to “forgot” about request without sending
anything (pretending reply was already sent).
Returning 204 should work as it returns correct HTTP reply with
empty content - but AFAIK at least IE have problems with it.
Thanks. I think I will just proxy the request to a Sinatra app, even though
I’m losing a lot of performance. Is that module for nginx 0.6.x?
It should work for both 0.6.* and 0.7.*.
Looks like it doesn’t compile with 0.7.53+ due to trivial unused
function declaration warning though. But it’s really trivial to
fix even without C knowledge (just remove offending line or
./configure nginx with --with-cc-opt="-Wno-error").