Re: duplicating or forking incoming requests

2013-07-12 Thread Gary Foster
Thanks, that did the trick exactly! Now that I have something that works, I'm off to the docs to figure out where my fundamental misunderstandings were and correct them. Very much appreciated! -- Gary F. On Jul 12, 2013, at 1:04 PM, Maxim Dounin wrote: > Hello! > > On Fri, Jul 12, 2013 at 1

Re: duplicating or forking incoming requests

2013-07-12 Thread Maxim Dounin
Hello! On Fri, Jul 12, 2013 at 12:47:02PM -0700, Gary Foster wrote: [...] > Here's the configuration snippets I'm currently using: > > location = /events { > access_log events_access.log events_format; > expires 1s; > try_files @proxy @proxy; > # try_files @proxy /empty.html;

duplicating or forking incoming requests

2013-07-12 Thread Gary Foster
I'm trying to figure out how to accomplish something with nginx and it seems to have me baffled. We use nginx as an endpoint to log incoming events. The default response is a 200, empty body and an entry in the access log in a very specific format. For legacy reasons, this will not change any