El mar., 20 nov. 2018 a las 8:56, Maxim Dounin () escribió:
>
> Hello!
>
> On Tue, Nov 20, 2018 at 08:43:52AM -0600, Ricky Gutierrez wrote:
>
> > Hi Dounin , What do you mean with smaller cache size?, proxy buffer size
> > for example?
>
> I mean keepalive connections cache size, as set to 15 in yo
Hello Dmitry,
Thanks for your answer. I understand locations can be configured to proxy
to external locations and therefore be used in subrequests from njs. That
is what I am doing for now. I consider this to be a workaround. Before I
explain why, I should explain the basics of my pet project. You
Hello!
On Wed, Nov 21, 2018 at 01:47:40PM -0500, Ortal wrote:
> Hi,
> I am developing my own nginx module, I am getting a post requests, parse the
> data and send 204.
> I worked with nginx version release-1.9.15, and I am trying to upgrade to
> version release-1.15.5.
> After the upgrade post r
Hi,
I am developing my own nginx module, I am getting a post requests, parse the
data and send 204.
I worked with nginx version release-1.9.15, and I am trying to upgrade to
version release-1.15.5.
After the upgrade post requests with payload larger then 1M are getting
blocked.
>From the nginx lo
Hello!
On Wed, Nov 21, 2018 at 08:53:40AM +, Rob Fulton wrote:
> On 19/11/2018 13:12, Maxim Dounin wrote:
> >
> > If you want to use variables in the proxy_pass and at the same
> > time want to preserve effect of nginx internal URI changes such as
> > due to rewrites, consider using an empty
Hi,
On 19/11/2018 13:12, Maxim Dounin wrote:
If you want to use variables in the proxy_pass and at the same
time want to preserve effect of nginx internal URI changes such as
due to rewrites, consider using an empty URI compontent in the
proxy_pass. For example:
set $backend "http://examp
