Hello!
On Wed, Sep 25, 2013 at 08:41:44PM -0400, Jeroen Ooms wrote:
> One more question regarding this:
>
> > The
> >proxy_no_cache $request_body_file;
> > should do the trick, see http://nginx.org/r/proxy_no_cache.
>
> I tried this and get a warning:
>nginx: [warn] "proxy_no_cache" fun
One more question regarding this:
> The
>proxy_no_cache $request_body_file;
> should do the trick, see http://nginx.org/r/proxy_no_cache.
I tried this and get a warning:
nginx: [warn] "proxy_no_cache" functionality has been changed in
0.8.46, now it should be used together with "proxy_cach
Hello!
On Sat, Sep 14, 2013 at 11:15:39AM -0700, Jeroen Ooms wrote:
> @ Maxim Dounin
>
> Thanks! This is very helpful. I have also set:
>
> client_body_buffer_size 1m;
>
> Could this setting have any side effects? I am not expecting too many
> large POST request. From what I read, client_body_
@ Maxim Dounin
Thanks! This is very helpful. I have also set:
client_body_buffer_size 1m;
Could this setting have any side effects? I am not expecting too many
large POST request. From what I read, client_body_buffer_size is
actually the maximum amount of memory allocated. Does this mean that
fo
Hello!
On Fri, Sep 13, 2013 at 05:56:51PM -0700, Jeroen Ooms wrote:
> Is it correct that when $content_length > client_body_buffer_size,
> then $request_body == "" ? If so this would be worth documenting at
> request_body.
Yes, it's intended behaviour. If a request body is larger than
client_b
Is it correct that when $content_length > client_body_buffer_size,
then $request_body == "" ? If so this would be worth documenting at
request_body.
I am using:
proxy_cache_methods POST;
proxy_cache_key "$request_method$request_uri$request_body";
Which works for small requests, but for l
