Re: Example body filter hangs when modified a little bit - request is not terminating.

here is with the body filter disabled (works normally): HTTP/1.1 200 OK Server: nginx/1.12.0 Date: Thu, 11 Jan 2018 04:16:07 GMT Content-Type: text/html Transfer-Encoding: chunked Connection: keep-alive here is with the body filter enabled (connection does not terminate): HTTP/1.1 200 OK

Re: Example body filter hangs when modified a little bit - request is not terminating.

Hi! what’s the corresponding response headers of your browser? ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx

Example body filter hangs when modified a little bit - request is not terminating.

I tried out this nginx example ngx_http_foo_body_filter body filter (here http://nginx.org/en/docs/dev/development_guide.html#http_body_buffers_reuse ) and got that to work just fine. It inserts a "foo" string before each incoming buffer. I tried modifying a little bit so that it puts the foo

Re: Secure Link Expires - URL Signing

On Wed, Jan 10, 2018 at 01:32:00PM -0500, anish10dec wrote: Hi there, > Let me explain the complete implementation methodology and problem > statement > > URL to be protected > http://site.media.com/mediafiles/movie.m3u8 > > We are generating token on application/client side to send it along

499 and set $loggable 0;

Any idea on how to keep those 499 errors out of the logs? I already do it for some specific 444 if specific condition { set $loggable 0; return 444; } Posted at Nginx Forum: https://forum.nginx.org/read.php?2,278092,278092#msg-278092 ___ nginx

Re: upstream (tcp stream mode) doesn't detect connecton failure

On 01/10/2018 07:58 PM, Maxim Dounin wrote: Hello! On Wed, Jan 10, 2018 at 07:18:36PM +0100, Adam Cecile wrote: [...] Ok, so you use multiple proxy layers to be able to combine backends which support/need PROXY protocol and ones which do not, right? This looks like a valid reason, as

Re: Secure Link Expires - URL Signing

Only the server should be generating the tokens, if the client knows the secret it can do whatever it wants. On Wed, Jan 10, 2018 at 10:32 AM, anish10dec wrote: > Let me explain the complete implementation methodology and problem > statement > > URL to be protected

Re: Secure Link Expires - URL Signing

Let me explain the complete implementation methodology and problem statement URL to be protected http://site.media.com/mediafiles/movie.m3u8 We are generating token on application/client side to send it along with request so that content is delivered by server only to authorized apps. Token

Re: upstream (tcp stream mode) doesn't detect connecton failure

On 01/10/2018 05:54 PM, Maxim Dounin wrote: Hello! On Tue, Jan 09, 2018 at 11:48:54PM +0100, Adam Cecile wrote: On 01/09/2018 02:46 PM, Maxim Dounin wrote: Hello! On Mon, Jan 08, 2018 at 12:37:41PM +, Cecile, Adam wrote: Hello, I'm using this quite complicated setup involving SNI

Re: upstream (tcp stream mode) doesn't detect connecton failure

Hello! On Tue, Jan 09, 2018 at 11:48:54PM +0100, Adam Cecile wrote: > On 01/09/2018 02:46 PM, Maxim Dounin wrote: > > Hello! > > > > On Mon, Jan 08, 2018 at 12:37:41PM +, Cecile, Adam wrote: > > > >> Hello, > >> > >> > >> I'm using this quite complicated setup involving SNI routing and > >>

Re: [PATCH] -h output note addition: Testing of configuration can lead to a correction of path/file permissions

Hello! On Wed, Jan 10, 2018 at 04:09:11PM +0100, Jörg Kost wrote: > # HG changeset patch > # User Joerg Kost > # Date 1515599827 -3600 > # Wed Jan 10 16:57:07 2018 +0100 > # Node ID 9132d6facd3ddbc9c50543a96686374b6e058f10 > # Parent

[PATCH] -h output note addition: Testing of configuration can lead to a correction of path/file permissions

# HG changeset patch # User Joerg Kost # Date 1515599827 -3600 # Wed Jan 10 16:57:07 2018 +0100 # Node ID 9132d6facd3ddbc9c50543a96686374b6e058f10 # Parent 6d2e92acb013224e6ef2c71c9e61ab07f0b03271 Modified cli help output to make it clear that nginx may modify permissions

Reverse proxy error on proxy_pass with redirect on backends to root

Hi All, I have been trying to configure our xen-orchestrator environment (application frontend for controlling Xen servers), published on a host on port 80. We tried their recommended configuration for NGINX after trying some others created by ourself but none of them seem to work. The recommended

Не работает редирект в mozilla.

Пытаюсь сделать редирект с https://www.lan-ip.ru/ на https://lan-ip.ru/ Во всех браузерах работает а в mozilla нет. Мой конфиг server { server_name www.lan-ip.ru; return 301 https://lan-ip.ru$request_uri; } server { listen 80; listen [::]:80; server_name

Re: Nginx error log parser

Hi All, I have something like this. I tested the `tail -f /var/log/nginx/error.log | awk -f /var/log/nginx/test.awk` part and it just works fine. But when i try to run it through fluentd, it doesn't do anything. Any idea why ? @type exec format json tag sample

Re: Nginx error log parser

Aziz Rozyev Wrote: --- > Hi Mohit, > > check the second reply. I’m not sure that there is a conventional > pretty printing > tools for nginx error log. Look at awstats. Posted at Nginx Forum:

Re: Nginx error log parser

Thanks Aziz for this, I get your point, but can we do awking in fluentd cons file ? Basically we are looking for realtime awking a nginx error log file, how heavy this would be according to you. On 10 January 2018 at 17:44, Aziz Rozyev wrote: > If you need parse exactly the

Re: Nginx error log parser

If you need parse exactly the same format, as you’ve shown in you question, it’s fairly easy to create something e.g. perl/awk/sed script. for instance: # tst.awk # BEGIN {FS = "," } { split($1, m, "\ ") printf "%s", "{ " printf "%s",$2 printf

Re: Nginx error log parser

Yeah I have tried grok / regex pattern as well. But not extensive success that I achieved. grok didn't work for me, I tried regex then it was able to segregate time , pid, tid, log_level and message. I also need message break up for above pattern On 10 January 2018 at 17:12, Aziz Rozyev

RE: NTLM

Hi Maxim, -Original message- From: Maxim Konovalov  Sent: Wednesday 10th January 2018 12:40 To: nginx@nginx.org; Otto Kucera Subject: Re: NTLM Hi Otto, On 10/01/2018 14:37, Otto Kucera wrote: > Hi all, > > > I am testing ntlm for a reverse proxy

Re: Nginx error log parser

Hi Mohit, check the second reply. I’m not sure that there is a conventional pretty printing tools for nginx error log. br, Aziz. > On 10 Jan 2018, at 14:37, mohit Agrawal wrote: > > Hi Aziz, > > log_format directive only provides formatting for access log, I am

Re: NTLM

Hi Otto, On 10/01/2018 14:37, Otto Kucera wrote: > Hi all, > > > I am testing ntlm for a reverse proxy secanrio. [...] > I always get this error: > > nginx: [emerg] *unknown directive "ntlm"* in > /etc/nginx/conf.d/test.conf:4 > > > This is my version: >

Re: NTLM

It’s only available for nginx-plus Get Outlook for iOS From: nginx on behalf of Otto Kucera Sent: Wednesday, January 10, 2018 12:37:49 PM To: nginx@nginx.org Subject: NTLM Hi all, I am testing

NTLM

Hi all, I am testing ntlm for a reverse proxy secanrio. Info: http://nginx.org/en/docs/http/ngx_http_upstream_module.html#ntlm this is my config: upstream http_backend { server 127.0.0.1:8080; ntlm; } server

Re: Nginx error log parser

Hi Aziz, log_format directive only provides formatting for access log, I am looking to format error.log which doesn't take log_format directive. Above example that I gave is just for nginx error logs. Thanks On 10 January 2018 at 15:26, Aziz Rozyev wrote: > btw, after

Re: Redirect request based on request type in case of error

On Tue, Jan 09, 2018 at 01:04:22AM -0500, devkuamr wrote: Hi there, > I want to redirect GET request to another server in case of errors. I am > using the below configuration but nginx is having problem while starting > with this configuration. > if

Re: Nginx error log parser

btw, after re-reading the your questing, it looks like you need something like logstash grok filter. br, Aziz. > On 10 Jan 2018, at 11:45, mohit Agrawal wrote: > > Hi , > > I am looking to parse nginx error log so as to find out which particular IP > is throttled

Country Based vhost include !!

Hi, We want to include virtual hosts based on the country such as, if country is "mycountry" include virtual.conf otherwise include default.conf. However, we tried to achieve that using 'if' but it doesn't support 'include' directive. Is there any other way of achieving this goal ? Thanks.

Re: Nginx error log parser

is the 'log_format json’ is what you’re asking for? http://nginx.org/en/docs/http/ngx_http_log_module.html#log_format br, Aziz. > On 10 Jan 2018, at 11:45, mohit Agrawal wrote: > > Hi , > > I am looking to parse nginx error log so as to find out which particular

Re: Secure Link Expires - URL Signing

On Wed, Jan 10, 2018 at 03:15:05AM -0500, anish10dec wrote: > URL Signing by Secure Link MD5 , restricts the client from accessing the > secured object for limited time using below module It can, if you configure it to. > Exp time is sent as query parameter from client device > > secure_link

Nginx error log parser

Hi , I am looking to parse nginx error log so as to find out which particular IP is throttled during specific amount of time on connection throttling / request throttling. The format looks like : 2018/01/10 06:26:31 [error] 13485#13485: *64285471 limiting connections by zone "rl_conn", client:

Re: IPv6 does not work correctly with nginx

On Fri, Jan 05, 2018 at 01:23:47PM +, Mik J via nginx wrote: Hi there, I don't have a direct solution to the issue you report. I do have a few things to try, which might help isolate where the problem is (and therefore where the fix should be). > The port seems open but there is no ssl

Secure Link Expires - URL Signing

URL Signing by Secure Link MD5 , restricts the client from accessing the secured object for limited time using below module Exp time is sent as query parameter from client device secure_link $arg_hash,$arg_exp; secure_link_md5 "secret$arg_exp"; if ($secure_link = "") {return 405;} if