You'll want to proxy_pass to a named upstream with keepalive enabled.
http://nginx.org/en/docs/http/ngx_http_upstream_module.html#keepalive
On Mon, Feb 13, 2017 at 11:33 PM, brookscunningham <
nginx-fo...@forum.nginx.org> wrote:
> Hello All,
>
> I am seeing an increase in the number of new TLS c
Hello All,
I am seeing an increase in the number of new TLS connections to my origin
server when using NGINX as a reverse proxy. I am offloading TLS at NGINX and
starting a new TLS connection to the origin.
The workflow is as follows:
client --> NGINX --> origin server
I would expect NGINX to e
On Mon, Feb 13, 2017 at 10:23:44AM +0100, Daniel wrote:
Hi there,
> i create a vhost confuguration for a vhost but i ma not able to access
> /vakanz for exmaple.
> I got a 404 error on the access logs.
> I Tried already with rewrite rules and i also tried with locations, no matter
> what i do,
We are using the DN of a user's certificate to identify them in the system.
This makes for a better user experience once they have installed their
certificates. But having the backing services have to parse the DN just to
get something readable is annoying at the least. But the way things are
movin
Hello!
On Mon, Feb 13, 2017 at 10:19:36AM -0500, Alex Addy wrote:
> While testing the new $ssl_client_s_dn variable (as of 1.11.6) I discovered
> that it doesn't handle unicode characters correctly, Say if I had a user
> cert with a DN of 'CN=доверенная третья сторона' after going through nginx
>
While testing the new $ssl_client_s_dn variable (as of 1.11.6) I discovered
that it doesn't handle unicode characters correctly, Say if I had a user
cert with a DN of 'CN=доверенная третья сторона' after going through nginx
it becomes 'CN=\D0\B4\D0\BE\D0\B2\D0\B5\D1\80\D0\B5\D0\BD\D0\BD\D0\B0\D1\8F
Hello!
On Mon, Feb 13, 2017 at 07:16:00AM -0500, MichaelLogutov wrote:
> Maxim Dounin Wrote:
> ---
> > Hello!
> >
> > On Sat, Feb 11, 2017 at 04:06:29PM -0500, MichaelLogutov wrote:
> >
> > > Hello.
> > > We have some strange issues when reque
Maxim Dounin Wrote:
---
> Hello!
>
> On Sat, Feb 11, 2017 at 04:06:29PM -0500, MichaelLogutov wrote:
>
> > Hello.
> > We have some strange issues when requests seems to stall inside
> nginx - in
> > nginx log we see that request took 1 second (a
Assuming a configuration with multiple similar 'listen' and
'server_name' statements, only the first one will work:
server {
listen 9090;
return 404;
server_name example.com;
}
server {
listen 9090;
return 403;
server_name example.com;
Hi,
i create a vhost confuguration for a vhost but i ma not able to access /vakanz
for exmaple.
I got a 404 error on the access logs.
I Tried already with rewrite rules and i also tried with locations, no matter
what i do, nothing works.
Anyone has an idea what can i do?
Cheers
Daniel
s
10 matches
Mail list logo