Hello!
On Mon, Sep 01, 2014 at 11:34:07AM +0100, Nick Kew wrote:
> On Fri, 2014-08-29 at 17:26 +0400, Maxim Dounin wrote:
>
> > In either case, you may want to consider using request body
> > filters instead, as recently discussed here:
> >
> > http://mailman.nginx.org/pipermail/nginx-devel/20
On Monday 01 September 2014 11:34:07 Nick Kew wrote:
[..]
> (That's against the 1.7.4 tarball: I didn't find anything looking
> like a dev repo).
[..]
http://hg.nginx.org/
wbr, Valentin V. Bartenev
___
nginx-devel mailing list
nginx-devel@nginx.org
h
On Fri, 2014-08-29 at 17:26 +0400, Maxim Dounin wrote:
> In either case, you may want to consider using request body
> filters instead, as recently discussed here:
>
> http://mailman.nginx.org/pipermail/nginx-devel/2014-August/005781.html
If I'm to use such a feature when it's uncommitted becau
Hello!
On Fri, Aug 29, 2014 at 01:51:55AM +0100, Nick Kew wrote:
> I have a filter that may want to rewrite request bodies.
>
> Stream-editing an nginx chain is straightforward enough
> (the equivalent output filter works fine).
> But as I understand it, I need to cater for a case where
> a requ
I have a filter that may want to rewrite request bodies.
Stream-editing an nginx chain is straightforward enough
(the equivalent output filter works fine).
But as I understand it, I need to cater for a case where
a request body is in r->request_body->temp_file.
Assuming it's there for a reason, I
