On Fri, Jan 25, 2019 at 03:28:42PM -0500, nenaB wrote:
Hi there,
None of the suggestions below are fully tested by me, so they are not
drop-in answers to your questions.
> I have nginx configured to cache certain requests mapped by
> tenant/host/uri/args - these files wouldn't change often, but
On Thu, Jan 31, 2019 at 05:25:00PM -0500, c0nw0nk wrote:
Hi there,
> The access.log file shows
>
> query1=param1&query2=param2
>
> All on the same line isit possible to split these up onto diifferent lines.
>
> Example.
>
> query1=param1
>
> query2=param2
I think "no", using just stock ngi
Hi Roman,
Thank you very much. I will study the source of the modules you mention, I
had not realised there were examples of this being done in core NGINX (and
in the future direct development questions to the correct mailing list!).
Alex
Posted at Nginx Forum:
https://forum.nginx.org/read.php?
Hi Alex,
On Tue, Feb 05, 2019 at 07:29:19AM -0500, abmackenzie wrote:
> Hi all,
>
> I am attempting to develop an NGINX module which is required to modify the
> response headers based on the content of the response body, whether from an
> upstream proxy or being fulfilled by the server itself.
>
Hi all,
I am attempting to develop an NGINX module which is required to modify the
response headers based on the content of the response body, whether from an
upstream proxy or being fulfilled by the server itself.
My current approach, a body filter, does not seem fruitful. By the time the
body f
