Redirect from HTTP to HTTPS does not work

2015-08-10 Thread StSch
This is my configuration: server { listen 80; server_name shell.*; return 301 https://$server_name$request_uri; } server { listen 443 ssl; server_name shell.*; location / { proxy_pass http://192.168.0.16:4200; } } I am using a Dynamic DNS Service to access NGINX running on m

proxy_set_header concatenated value

2015-08-10 Thread Igal @ Lucee.org
hi, I want to pass the following header to the backend server: name: X-Original-URL value: $scheme://$host$request_uri but the concatenation of the values for the value above do not seem to work. how can I do that? thanks, -- Igal Sapir Lucee Core Developer Lucee.org

Nginx & Digest authentication

2015-08-10 Thread Arun John (arujohn)
I have a NGINX that sits in front of my application. I have digest authentication enabled for the application. I’d like a set up where when a user connects to NGINX using Digest, NGINX simply proxies this request to my application where the actual authentication happens. The authentication logic

Re: ssl_password_file on nginx 1.8.0

2015-08-10 Thread B.R.
At first I thought the 0x0a character could be a problem, though highly improbable... then I realized that one of the server blocks using that certificate had no ssl_password_file configured. Shameful mistake created a dummy error. Sorry for bothering! Thanks for help. --- *B. R.* On Mon, Aug 10,

Odd server_name directive behavior

2015-08-10 Thread CJ Ess
I have an nginx 1.9.0 deploy and I noticed a working config where the name given to the server_name directive doesn't match the names in the Host headers or the certificate DNs. It looks like a mistake, but it works, and I don't know why! Is it possible that if there is only one server stanza that

Re: ssl_password_file on nginx 1.8.0

2015-08-10 Thread Valentin V. Bartenev
On Saturday 08 August 2015 17:05:26 B.R. wrote: > Hello, > > I cannot manage to load a certificate protected wit ha password on nginx > 1.8.0: > [emerg] 2331#0: SSL_CTX_use_PrivateKey_file("/etc/ssl/private/domain.key") > failed (SSL: error:0906406D:PEM routines:PEM_def_callback:problems getting >

Proxy non persistent client connections to persistent upstream connections

2015-08-10 Thread Richard Jennings
I would like to be able to proxy non persistent client http connections to persistent upstream connections on a Linux system, both to reduce the number of connections and the upstream latency. I have experimented with keepalive and proxy_pass. To observe performance I used log_format upstreamlog