Many Thanks Maxim,
But we did try to achieve the functionality by using - nginx=1.10.3-r1, we
couldn't get request based session stickiness.
Basically we want the requests with identical query params to hit the same
instance everytime.
By recompiling again with this module and using below config
I didn't get full reply, Maxim,.. Could you please reply again..
On Wed 19 Sep, 2018, 11:53 PM Maxim Dounin, wrote:
> Hello!
>
> On Wed, Sep 19, 2018 at 06:40:11PM +0530, Devika Awasthi wrote:
>
> > I have a question on Nginx open source.
> >
> > So, we have a nginx web server being used as kub
Hello!
On Wed, Sep 19, 2018 at 03:59:58PM -0400, kpuscas wrote:
> Our service uses 2-way ssl with our clients connecting to our systems. With
> each new client we add their intermediate and root CA chain to the
> concatenated certificates file used by ssl_client_certificate. We recently
> upgrade
Our service uses 2-way ssl with our clients connecting to our systems. With
each new client we add their intermediate and root CA chain to the
concatenated certificates file used by ssl_client_certificate. We recently
upgraded to 1.14.0 (and the included modules) and now some, but not all of
our c
Hello!
On Wed, Sep 19, 2018 at 06:40:11PM +0530, Devika Awasthi wrote:
> I have a question on Nginx open source.
>
> So, we have a nginx web server being used as kubernetes pod in production
> as reverse proxy and web layer.
>
> We wanted to leverage the upstream hash module for session sticki
Hello!
On Wed, Sep 19, 2018 at 11:25:49AM +0300, Palvelin Postmaster via nginx wrote:
> I believe my current rexexp match isn’t proper because it’s missing an anchor
> from the pattern:
>
> location ~ /\. {
> deny all;
> }
>
> What would be more appropriate? Would this work?
>
> locatio
Hello!
On Wed, Sep 19, 2018 at 02:19:53AM -0400, winger7 wrote:
> I've been trying to identify the last HTTP request from a buffer of 10
> requests sent on a TCP connection in nginx. I've tried to use the header_in
> field in the ngx_http_request_t by checking if the pos field for the
> header_in
Hello everyone,
We are using a custom Nginx plugin to tag (setsockopt) response (per domain)
traffic from Nginx with QoS DSCP flag and that is working fine, however we are
seeing that SSL handshake responses are not getting tagged. Once handshake is
done the rest of the responses are tagged as
Hi Team,
I have a question on Nginx open source.
So, we have a nginx web server being used as kubernetes pod in production
as reverse proxy and web layer.
We wanted to leverage the upstream hash module for session stickiness. We
tried a POC locally by recompiling the Nginx with additional m
Maxim Dounin Wrote:
---
> Hello!
>
> On Tue, Sep 18, 2018 at 06:02:46AM -0400, domleb wrote:
>
> > While running a load test that injects 10k TPS across 3 Nginx
> instances, we
> > are seeing spikes of errors where Nginx returns HTTP 502 and log
tks Anoop
Em 19/09/2018 07:51, Anoop Alias escreveu:
location ~ /\.
regex location for /.
The back slash before dot is just an escape char as dot has special
meaning in regex
---
location ~ \.php$
regex location for anything ending in .php
He
Thanks Sergey
On Wed, Sep 19, 2018 at 4:24 PM Sergey Kandaurov wrote:
>
> > On 19 Sep 2018, at 05:41, Anoop Alias wrote:
> >
> > Hi,
> >
> > ./configure --prefix=/etc/nginx --sbin-path=/usr/sbin/nginx
> --with-openssl=./openssl-1.1.1
> > make DESTDIR=/opt/test install
> >
> > Did not create the
> On 19 Sep 2018, at 05:41, Anoop Alias wrote:
>
> Hi,
>
> ./configure --prefix=/etc/nginx --sbin-path=/usr/sbin/nginx
> --with-openssl=./openssl-1.1.1
> make DESTDIR=/opt/test install
>
> Did not create the .openssl directory inside the openssl source , but
> instead, this created the .op
location ~ /\.
regex location for /.
The back slash before dot is just an escape char as dot has special meaning
in regex
---
location ~ \.php$
regex location for anything ending in .php
Here again the backslash before dot serve as an escape
On We
Dears, in me Lab i have nginx work fine, but i dont understood the
diretive location with regex "~ /\. " "~* \." and
"~ \.php$" bellow examples in me enviroment.
location ~ /\. {
deny all;
access_log off;
log_not_found off;
}
Hello Greg,
19.09.2018 04:35, Greg Barker wrote:
> Seems like maybe something is broken on the nginx packages download.
>
> For example, if I curl this endpoint I get a set of results from 31-Jul-2018
>
> $ curl https://nginx.org/packages/rhel/7/x86_64/repodata/
> ...
> The result is that you do
Why am I getting these log warn/emerg? Running Nginx 1.14.0 on Ubuntu 18.04.
root@k2:~# whoami
root
root@k2:~# service nginx restart
root@k2:~# tail /var/log/nginx/error.log
2018/09/19 11:38:47 [warn] 22399#22399: the "user" directive makes sense only
if the master process runs with super-user
I believe my current rexexp match isn’t proper because it’s missing an anchor
from the pattern:
location ~ /\. {
deny all;
}
What would be more appropriate? Would this work?
location ~ /\..*$
--
Palvelin.fi Hostmaster
postmas...@palvelin.fi
18 matches
Mail list logo
