.service ExecStartPre in example

2019-01-11 Thread Olaf van der Spek
What's the purpose of testing the configuration file in the systemd example? Just starting the server seems simpler.. and the test isn't run prior to a restart request. ExecStartPre=/usr/sbin/nginx -t https://www.nginx.com/resources/wiki/start/topics/examples/systemd/ Posted at Nginx Forum:

set up TLS/ DTLS terminations for TCP/UDP connections

2019-01-11 Thread pietdinu
Hi all, I need to set up TLS/ DTLS terminations for TCP/UDP connections. The Ingress should be the solution to expose our services via TCP/UDP connections with TLS/ DTLS terminations. I'm using nginx version: 1.15.3 Is it possible to set up TLS/DTLS terminations for TCP/UDP connections?

Re:Re: share cookies between servers

2019-01-11 Thread David Ni
Hi Francis, Thanks very much for your point! I have read some info from internet based on your suggestion,for my understanding: when I login to one of the server datanode02.bddev.test.net,set cookie like this: server { listen 80; server_name datanode02.bddev.test.net;

Re: .service ExecStartPre in example

2019-01-11 Thread Lucas Rolff
There's nothing wrong with testing the configuration before starting the web server. The config is tested during restart, by the ExecStartPre. If you modify a config and you want to restart, you should execute nginx -t prior to restarting your service - but generally you'd want to use nginx -s

Default TLS v1.3 support in nginx 1.13.0+ Pre-Built packages

2019-01-11 Thread Leonard via nginx
Hello, I would be glad if nginx 1.13.0+ were to be compiled by default with openssl 1.1.1, so that by default the TLS v1.3 support is activated. This concerns the Pre-Built packages in the nginx repository. I'm running Debian GNU/Linux 9.6 (stretch). Information on `nginx -V`: */nginx version:

Re: set up TLS/ DTLS terminations for TCP/UDP connections

2019-01-11 Thread Maxim Konovalov
Hi Pietro, On 11/01/2019 16:46, pietdinu wrote: > Hi all, > > I need to set up TLS/ DTLS terminations for TCP/UDP connections. > The Ingress should be the solution to expose our services via TCP/UDP > connections with TLS/ DTLS terminations. > I'm using nginx version: 1.15.3 > > Is it

Location

2019-01-11 Thread petrosetta
Hi All I am trying to redirect to an internal server behind nginx that I really have no permissions to change. When you browse to the site normally at https://www.devapp.com for example it redirects to https://www.devapp.com/webaccess and it comes up fine. When I put in the nginx entries for it

Re: Location

2019-01-11 Thread basti
On 11.01.19 17:35, petrosetta wrote: > Hi All > I am trying to redirect to an internal server behind nginx that I really > have no permissions to change. When you browse to the site normally at > https://www.devapp.com for example it redirects to > https://www.devapp.com/webaccess and it comes

Re: .service ExecStartPre in example

2019-01-11 Thread Olaf van der Spek
Lucas Rolff Wrote: --- > There's nothing wrong with testing the configuration before starting > the web server. Sure, but what effect does it have in the .service file? > The config is tested during restart, by the ExecStartPre. If you But

Re: Location

2019-01-11 Thread basti
On 11.01.19 19:51, petrosetta wrote: > HI > Thanks so much for replying. Below is the block and upstream entry. Also, > let's say without NGINX I bring up the site at > https://mysite.domain.com/webaccess, when I click on an image, the url is > https://mysite.domain.com/name_of_image. > >

Re: Location

2019-01-11 Thread petrosetta
HI Thanks so much for replying. Below is the block and upstream entry. Also, let's say without NGINX I bring up the site at https://mysite.domain.com/webaccess, when I click on an image, the url is https://mysite.domain.com/name_of_image. upstream devapp { server

Re: Location

2019-01-11 Thread basti
On 11.01.19 20:44, petrosetta wrote: > It works perfectly. Thanks very much. If you could bear with me a little > though,What if I wanted to also put the prod web site behind nginx, I can't > use more than one root location so how could that be done. The only > difference with the name is prod is

Re: Location

2019-01-11 Thread petrosetta
It works perfectly. Thanks very much. If you could bear with me a little though,What if I wanted to also put the prod web site behind nginx, I can't use more than one root location so how could that be done. The only difference with the name is prod is prodapp instead of devapp. Posted at Nginx

Re: Location

2019-01-11 Thread petrosetta
:) Understood. Well Ideally what I would like is: 1. An outside user hits https://www.mydomain.com he hits NGINX which redirects him to the internal site https://app.mydomain.com. 2. An outside user hits https://www.mydomain.com/webdev NGINX redirects him to the internal site

Re: Default TLS v1.3 support in nginx 1.13.0+ Pre-Built packages

2019-01-11 Thread Maxim Dounin
Hello! On Fri, Jan 11, 2019 at 11:44:30AM +0100, Leonard via nginx wrote: > I would be glad if nginx 1.13.0+ were to be compiled by default with > openssl 1.1.1, so that by default the TLS v1.3 support is activated. > This concerns the Pre-Built packages in the nginx repository. > > I'm running

[njs] Refactored njs_function_lambda_call().

2019-01-11 Thread Dmitry Volyntsev
details: https://hg.nginx.org/njs/rev/8fb687d866de branches: changeset: 726:8fb687d866de user: hongzhidao date: Fri Jan 11 18:57:57 2019 +0800 description: Refactored njs_function_lambda_call(). diffstat: njs/njs_function.c | 35 +

[njs] Improved an argument name of njs_function_frame().

2019-01-11 Thread Dmitry Volyntsev
details: https://hg.nginx.org/njs/rev/fb2c2bca61c2 branches: changeset: 727:fb2c2bca61c2 user: hongzhidao date: Fri Jan 11 19:20:38 2019 +0800 description: Improved an argument name of njs_function_frame(). diffstat: njs/njs_function.c | 8 njs/njs_function.h | 6