Let's start with some background. I'm developing a module to run
inside the NGINX engine to process requests (standard content phase)
against an API (not an upstream-compatible socket-based protocol).
These requests could be long-running so the module is using thread
tasks to execute and generate
Giving this one more try with a few questions this time.
1) This mailing list used to be more discussion oriented but seems to
be mainly patch notifications now. Is there a more appropriate
channel to ask these kind of module development questions for NGINX?
2) I'm actually working on a second m
Hmmm, hopefully this works because I subscribed with digest. Thank
you very much for the feedback, I now had an idea of where to focus (I
had a rough idea but this made it clearer). And now I know what the
issue is but have no idea how to resolve it.
My module was setting the upstream length as
Ok, that did it, was a bit more painful than expected since I had to
actually write a filter function (if you don't provide it, your init
method is also overwritten by the default) but in the end it is now
cleanly processing without hanging up on my upstream daemon.
A suggested change to consider
Hi all, I've asked this before with no response, trying one last time
before I just make something work.
I'm making a custom module for nginx that does a number of things but
one of the actions is a long-running (in the nginx sense) task that
could produce a large response. I've already got prope
age a kernel pipe buffers could be surely faster, but indirect you'd just
> relocate the potential OOM issue from nginx process to the system.
>
> Regards,
> Sergey
>
> 10.11.2020 02:54, Jeff Heisz wrote:
>
> Hi all, I've asked this before with no response, tr
Hello!
I've been trying to debug an issue with a custom nginx module, which
is working 'properly' with desktop browsers but failing on Apple
browsers with an 'invalid response' error message.
I don't know exactly what it doesn't like (so much fun debugging on
i-devices) but I am seeing one speci
course it makes sense in this case that there was a response length
but no body because I had forced the flag. Code adjusted, no more
invalid response errors on i-devices! Thanks for the help Maxim.
jmh
On Fri, Jan 13, 2023 at 11:19 PM Jeff Heisz wrote:
>
> Hello!
>
> I've been
