Re[6]: nginx restart AND listen ip:port

Третий и последний раз повторяю, хотите, чтобы вам помогли - обозначайте ВСЕ части конфига, отвечающие за проблему. То, что по вашему мнению должно работать, но не работает. Вы видите разницу в ваших локейшенах? Апстрим backend у вас как-то определен? В error.log, случаем, не проскакивает что-то

Re: Nginx 1.13.9 HTTP/2 Server Push - non-compressed assets ?

On Wed, Feb 14, 2018 at 06:19:01PM -0500, George wrote: > thanks Ruslan for the update appreciate all your work and looking forward to > playing with HTTP/2 Push finally ! :) Start off right today: https://www.youtube.com/watch?v=wR1gF5Lhcq0 ___ nginx

Re: [PATCH] HTTP/2: expose function to push single resource to modules

On Tue, Feb 13, 2018 at 04:31:17PM +0300, Maxim Dounin wrote: > Hello! > > On Tue, Feb 13, 2018 at 12:21:36PM +, Alessandro Ghedini wrote: > > > On Fri, Feb 09, 2018 at 10:35:59AM +0300, Ruslan Ermilov wrote: > > > On Thu, Feb 08, 2018 at 07:48:25PM +, Alessandro Ghedini wrote: > > > >

Re: Nginx 1.13.9 HTTP/2 Server Push - non-compressed assets ?

thanks Ruslan for the update appreciate all your work and looking forward to playing with HTTP/2 Push finally ! :) Posted at Nginx Forum: https://forum.nginx.org/read.php?2,278481,278582#msg-278582 ___ nginx mailing list nginx@nginx.org

Re: no access_log logging for UDP streams

On Wed, Feb 14, 2018 at 5:59 AM, Roman Arutyunyan wrote: > Hi David, > > On Tue, Feb 13, 2018 at 01:01:03PM -0800, David Kewley wrote: > > I'm using nginx 1.12.1 to proxy TCP and UDP streams. I have in my stream > {} > > stanza: > > > > log_format test '$time_local'; > > > >

Re: Response Header IF statement problem

Hi, Yes NGINX can inspect the header, See the following full example. It will check for the match of "true" case-insensitive. I am simulating your backend on port 81. Does this make sense? map $upstream_http_x_secured_page $nocache { ~*true "1"; default

Re: Response Header IF statement problem

Maybe that’s the problem, I want to disable cache if the response header is true but not do anything if it is false. I can change my logic in creating this header to only have it on pages where cache should be disabled if it is not possible to use an IF statement around it. I will post my

Re: Response Header IF statement problem

Hi, The map is processed on each request and should be very consistent. I thought you wanted to disable cache on the existence of a response header, not a request header. Otherwise I think we need more information to understand, such as how are you testing? Perhaps paste your full

Re: Response Header IF statement problem

Ok, so I did this and it worked and then it stopped working, then it worked again and then stopped working. I literally used the code below, the map appears right above my server {} block. When it worked I was passing a header with the $nocache value set and it was consistently returning the

Re: Nginx 1.13.9 HTTP/2 Server Push - non-compressed assets ?

On Sat, Feb 10, 2018 at 01:21:16PM -0500, George wrote: > Hi compiled Nginx 1.13.9 from master branch to try out HTTP/2 Server Push > but noticed the pushed assets loose their gzip compression and are served as > non-compressed assets ? Is that as intended ? I posted my findings at >

Re: [PATCH] HTTP/2: added support for setting custom push request headers

On Tue, Feb 13, 2018 at 11:58:40AM +, Alessandro Ghedini wrote: > If it's of any help, I merged your patch and mine into one, which copies the > headers (excluding Accept) into PUSH_PROMISE and r->headers_in like my > original > patch did, as well as HPACK encode them into PUSH_PROMISE

Re: Возможность проверить успешность auth_basic авторизации

Hello! On Thu, Feb 15, 2018 at 12:28:56AM +0700, Vadim A. Misbakh-Soloviov wrote: > Всем привет. > У меня тут возникла необходимость в проверке успешности auth_basic > авторизации > (каковая, например, есть для client_certificate ($ssl_client_verify)). > > У меня была идея сделать (средствами

Возможность проверить успешность auth_basic авторизации

Всем привет. У меня тут возникла необходимость в проверке успешности auth_basic авторизации (каковая, например, есть для client_certificate ($ssl_client_verify)). У меня была идея сделать (средствами NginX) basic-авторизацию (в одном и том же локейшне) необязательной, но принципиально

Re: nginx restart AND listen ip:port

Hello! On Wed, Feb 14, 2018 at 11:08:42AM -0500, imsystem wrote: > Спасибо ещё раз, посмотрю примеры init конфигов, насколько мне известно он > дефолтный. Для systemd - лучше написать сразу service-файл, или взять из официальных пакетов. Или же просто добавить отладочного вывода в

Re: Re[4]: nginx restart AND listen ip:port

Во второй записи backend = local_IP_IIS Posted at Nginx Forum: https://forum.nginx.org/read.php?21,278551,278569#msg-278569 ___ nginx-ru mailing list nginx-ru@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx-ru

Re: Re[4]: nginx restart AND listen ip:port

Всё проксирует, при записи server { listen external_IP_nginx:443; location / { proxy_pass https://local_IP_IIS; } } При этой записи не проксирует, выдавало, насколько помню, 403 server { listen 443; location / { proxy_pass https://backend; } } А прочие команды я и в документации видел, просто

Re: nginx restart AND listen ip:port

Спасибо ещё раз, посмотрю примеры init конфигов, насколько мне известно он дефолтный. Но, вы забыли изначальную причину данной "проблемы", в одном случае конфигурации listen, init скрипт срабатывает как надо, а во втором что-то идёт не так. Maxim Dounin Wrote:

Re[4]: nginx restart AND listen ip:port

Да, сопоставима. Просто вы об этом ничего не сказали. Насчет опции -s и прочих можете посмотреть nginx -h Будет что-то типа: nginx version: nginx/1.13.8 Usage: nginx [-?hvVtTq] [-s signal] [-c filename] [-p prefix] [-g directives] Options:   -?,-h : this help   -v    : show

Re: Response Header IF statement problem

Ok, I think this sends me into the correct direction. Thanks for posting the links and explaining the _bypass, I was setting both _bypass and _no_cache because I wasn’t sure. ___ Michael Friscia Office of Communications Yale School of Medicine (203)

Re: nginx restart AND listen ip:port

Hello! On Wed, Feb 14, 2018 at 09:58:28AM -0500, imsystem wrote: > systemctl status nginx > > ● nginx.service - LSB: starts the nginx web server >Loaded: loaded (/etc/init.d/nginx; generated; vendor preset: enabled) > Drop-In: /etc/systemd/system/nginx.service.d >└─limits.conf

Re: Response Header IF statement problem

You can use map for this... - http://nginx.org/en/docs/http/ngx_http_map_module.html#map map $upstream_http_x_secured_page $nocache { "search string" "1" default ""; } location /foo { ... proxy_no_cache $nocache; } Posted at Nginx Forum:

Re: Response Header IF statement problem

Thank you Roman, but this raises a different question, if I want to base this on the value and not the existence, is that still possible? ___ Michael Friscia Office of Communications Yale School of Medicine (203) 737-7932 - office (203) 931-5381 - mobile

Re: Response Header IF statement problem

Hi Michael, On Wed, Feb 14, 2018 at 02:09:57PM +, Friscia, Michael wrote: > I’m at a loss on this. I am working on a cache problem where some pages need > to be bypassed and others will be cached. So the web server is adding a > response header (X-Secured-Page). I’ve tried multiple

Re: nginx restart AND listen ip:port

systemctl status nginx ● nginx.service - LSB: starts the nginx web server Loaded: loaded (/etc/init.d/nginx; generated; vendor preset: enabled) Drop-In: /etc/systemd/system/nginx.service.d └─limits.conf Active: failed (Result: exit-code) since Wed 2018-02-14 17:46:35 MSK; 5s

Response Header IF statement problem

I’m at a loss on this. I am working on a cache problem where some pages need to be bypassed and others will be cached. So the web server is adding a response header (X-Secured-Page). I’ve tried multiple combinations of $http_x_secured_page and $sent_http_x_secured_page and even though I see the

Re: nginx restart AND listen ip:port

Hello! On Wed, Feb 14, 2018 at 07:56:10AM -0500, imsystem wrote: > restart|force-reload) > echo -n "Restarting $DESC: " > start-stop-daemon --stop --quiet --pidfile \ > /var/run/$NAME.pid --exec $DAEMON > sleep 1 > start-stop-daemon --start --quiet

Re: no access_log logging for UDP streams

Hi David, On Tue, Feb 13, 2018 at 01:01:03PM -0800, David Kewley wrote: > I'm using nginx 1.12.1 to proxy TCP and UDP streams. I have in my stream {} > stanza: > > log_format test '$time_local'; > > access_log /var/log/nginx/stream-access.log test buffer=64k flush=1s; > error_log

Re: nginx restart AND listen ip:port

restart|force-reload) echo -n "Restarting $DESC: " start-stop-daemon --stop --quiet --pidfile \ /var/run/$NAME.pid --exec $DAEMON sleep 1 start-stop-daemon --start --quiet --pidfile \ /var/run/$NAME.pid --exec $DAEMON -- $DAEMON_OPTS

Re: Re[2]: nginx restart AND listen ip:port

> Вам обязательно 'service nginx restart'? > 'nginx -s reload' пробовали? Нет, не обязательно. Нет, не пробовал, считал её сопоставимой команде service nginx reload, а она работает. Меня сам факт смущает. > Насчет версии 1.12.1. В stable ветке доступна 1.12.2. Может там уже > пофиксили? Может и

Re: nginx restart AND listen ip:port

Hello! On Wed, Feb 14, 2018 at 04:56:42AM -0500, imsystem wrote: > Здравствуйте. Обнаружил такую проблему(багу?). > При добавлении блока: > > server { > listen ip:80 default_server; > server_name _; > return 301 https://mysite.com; > } > > Перестаёт работать рестарт

Re[2]: nginx restart AND listen ip:port

Вам обязательно 'service nginx restart'? 'nginx -s reload' пробовали? Насчет версии 1.12.1. В stable ветке доступна 1.12.2. Может там уже пофиксили? >> Два интерфейса внешний и локальный. Везде ip - внешний ip. >> Проксирование идёт по локалке. >> Если принудительно не указывать ip в listen, то

Re: nginx restart AND listen ip:port

И совсем забыл. nginx -V nginx version: nginx/1.12.1 built by gcc 6.3.0 20170516 (Debian 6.3.0-18) built with OpenSSL 1.1.1-dev xx XXX TLS SNI support enabled configure arguments: --prefix=/usr/local/nginx/ --conf-path=/etc/nginx/nginx.conf --error-log-path=/var/log/nginx/error.log

Re: nginx restart AND listen ip:port

Добавлю что nginx используется для проксирования на backend. Два интерфейса внешний и локальный. Везде ip - внешний ip. Для сайтов блоки: server { listen ip:80 .. return ... } server { listen ip:443 .. ... } Проксирование идёт по локалке. Если принудительно не указывать ip в listen, то не

nginx restart AND listen ip:port

Здравствуйте. Обнаружил такую проблему(багу?). При добавлении блока: server { listen ip:80 default_server; server_name _; return 301 https://mysite.com; } Перестаёт работать рестарт сервера. Если же ip:80 заменить на просто порт 80, то команды service nginx restart или