Re: Transfering url arguments to different location

2014-04-02 Thread B.R.
Thanks Jonathan! However, not much details on why it is a 'hack' not to be trusted since unreliable. I do not rely on the Wiki anymore, and since Maxim specifically says it should be removed... I hope it will be, to prevent unreliable configurations to be shared and propagated based on unofficial

Re: Transfering url arguments to different location

2014-04-02 Thread Jonathan Matthews
On 2 April 2014 14:13, B.R. wrote: > If someone had details about reasons not to use post_action (either from the > referenced IIRC discussion or from other sources), I would be very > interested in them. http://forum.nginx.org/read.php?2,213627,213722#msg-213722 and the note on the wiki next to

Re: Transfering url arguments to different location

2014-04-02 Thread B.R.
On Wed, Apr 2, 2014 at 11:11 AM, Jonathan Matthews wrote: > As an aside, IIRC people @nginx have stated publicly that post_action is a > hack, and that its behaviour should not be relied on. I'm without Internets > right now so can't find you the quote, but it was sufficient to put me off > using

Re: Transfering url arguments to different location

2014-04-02 Thread Jonathan Matthews
On 2 Apr 2014 07:31, "Cristian Rusu" wrote: > > Hello > > I have a setup on nginx to count downloads. > > > location / {. > post_action /afterdownload; > > Here I have a value in $arg_key > > location /afterdownload { > > I need $arg_key here > > Any way to send it to /afterdownload se

Transfering url arguments to different location

2014-04-01 Thread Cristian Rusu
Hello I have a setup on nginx to count downloads. *location / {.post_action /afterdownload;* Here I have a value in $arg_key *location /afterdownload {* I need $arg_key here Any way to send it to /afterdownload section? Thank you ---