Re: Need help on Oauth-2.0 Token with Nginx reverse proxy

2019-07-30 Thread blason
Here are the error messages I am seeing in access.log 1.2.3.4 - - [31/Jul/2019:10:07:58 +0530] "POST /connect/token HTTP/1.1" 400 80 "https://test.example.net/; "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/75.0.3770.142 Safari/537.36" 1.2.3.4 - -

Re: Need help on Oauth-2.0 Token with Nginx reverse proxy

2019-07-30 Thread blason
blason Wrote: --- > Hi Folks, > > I am trying to setup a reverse proxy on nginx with server at backend > and from HAR file I understand it uses Oauth-Token-2.0 with POST > method. > > However I am unable to set the stuff and seeking help here.

Need help on Oauth-2.0 Token with Nginx reverse proxy

2019-07-30 Thread blason
Hi Folks, I am trying to setup a reverse proxy on nginx with server at backend and from HAR file I understand it uses Oauth-Token-2.0 with POST method. However I am unable to set the stuff and seeking help here. My original server here is assuming https://test.example.net:9084 And for Outh

handling cookie

2019-07-30 Thread Kuroishi Mitsuo
Hi, I'm developing a module that handles the cookie header for Nginx. It's kind of awkward though, the cookie sometimes contains the same key name. For example, Cookie: a=xxx; a=yyy Currently I use ngx_http_parse_multi_header_lines() like below. ngx_str_t buf; ngx_str_t key =

Why 301 permanent redirect with appended slash?

2019-07-30 Thread J. Lewis Muir
Hello, all! I have a minimal nginx.conf with one server block that sets the root directory and one location with a prefix string of "/foo/", and for a request of "/foo", it returns a 301 permanent redirect to "/foo/". Why? I expected it to return 404 or similar. I also tried a prefix string of

Implicit root location?

2019-07-30 Thread J. Lewis Muir
Hello, all! I have a minimal nginx.conf with one server block that sets the root directory but has *no* location directives, yet for a request of "/", it serves "/index.html". Why? With no locations specified, I expected it to return 404 or similar for any request. Here's the server block

[njs] Refactored usage of njs_ret_t.

2019-07-30 Thread Dmitry Volyntsev
details: https://hg.nginx.org/njs/rev/f4ac8168e856 branches: changeset: 1087:f4ac8168e856 user: Dmitry Volyntsev date: Tue Jul 30 21:12:08 2019 +0300 description: Refactored usage of njs_ret_t. Currently njs_ret_t is used in 2 different cases: as a jump offset for bytecode and as a

[njs] Refactored file hierarchy.

2019-07-30 Thread Dmitry Volyntsev
details: https://hg.nginx.org/njs/rev/8b01e5bbbd16 branches: changeset: 1086:8b01e5bbbd16 user: Dmitry Volyntsev date: Tue Jul 30 20:11:46 2019 +0300 description: Refactored file hierarchy. 1) all source files are moved to src directory. 2) nxt files are renamed with "njs" prefix.

Re: Crash in mail module during SMTP setup

2019-07-30 Thread Maxim Dounin
Hello! On Tue, Jul 30, 2019 at 06:32:43PM +0300, Maxim Dounin wrote: > Hello! > > On Tue, Jul 30, 2019 at 10:39:56PM +1000, Rob N ★ wrote: > > > On Tue, 30 Jul 2019, at 4:26 AM, Maxim Dounin wrote: > > > Looking at "p *c" and "p *s" might be also interesting. > > > > Program received signal

Re: Crash in mail module during SMTP setup

2019-07-30 Thread Maxim Dounin
Hello! On Tue, Jul 30, 2019 at 10:39:56PM +1000, Rob N ★ wrote: > On Tue, 30 Jul 2019, at 4:26 AM, Maxim Dounin wrote: > > Looking at "p *c" and "p *s" might be also interesting. > > Program received signal SIGSEGV, Segmentation fault. > 0x005562f2 in ngx_mail_smtp_resolve_name_handler

Re: Resident memory not released

2019-07-30 Thread fredr
Maxim Dounin Wrote: --- > > Whether or not allocated (and then freed) memory will be returned > to the OS depends mostly on your system allocator and its > settings. That is very interesting! I had no idea, thanks! Maxim Dounin Wrote:

Re: Crash in mail module during SMTP setup

2019-07-30 Thread Rob N ★
On Tue, 30 Jul 2019, at 4:26 AM, Maxim Dounin wrote: > Looking at "p *c" and "p *s" might be also interesting. Program received signal SIGSEGV, Segmentation fault. 0x005562f2 in ngx_mail_smtp_resolve_name_handler (ctx=0x7bcaa40) at src/mail/ngx_mail_smtp_handler.c:215 215

Re: zero size buf in writer in 1.17.2

2019-07-30 Thread Witold Filipczyk
On Mon, Jul 29, 2019 at 07:48:41PM +0300, Maxim Dounin wrote: > Hello! > > On Sun, Jul 28, 2019 at 04:32:18PM +0200, Witold Filipczyk wrote: > > > Hi, > > There is error in log: > > 2019/07/28 09:46:10 [alert] 2471467#2471467: *407 zero size buf in writer > > t:1 r:1 f:0 7F482A259000