Hi Lance,
On 2/10/23 7:10 PM, Lance Dockins wrote:
Thanks, Dmitry.
Is it correct to assume that this setting just forces all POST bodies
into a file (like shutting off client body buffers)? And would that be
true even with the “clean” directive?
>
> The “clean” value sounds like it just re
Thanks, Dmitry.
Is it correct to assume that this setting just forces all POST bodies into a
file (like shutting off client body buffers)? And would that be true even with
the “clean” directive?
The “clean” value sounds like it just retains the POST body file until the
request completes (at w
Hi Lance,
On 10.02.2023 18:24, Lance Dockins wrote:
This sort of NJS behavior "seems" like some sort of race condition
where NJS is trying to access the file after Nginx has already
disposed of it. Since this is a js_content directive, it should be
blocking and it seems to be one of the few s
If it matters, I’m using Nginx 1.23.3 and NJS 0.7.10
--
Lance Dockins
On Feb 10, 2023 at 8:24 PM -0600, Lance Dockins , wrote:
> NJS seems to be throwing an error when trying to access the temp body file
> created for POST bodies that are larger than the client body buffer size.
>
> I've verifi
NJS seems to be throwing an error when trying to access the temp body file
created for POST bodies that are larger than the client body buffer size.
I've verified that Nginx and NJS have access to this folder location. As a
test, I placed a permanent file in the body temp folder location and can
