Nginx proxy_pass URL-encoding with "unsafe" characters is not working

Hi all, on my Nginx (1.16.0) I noticed the following behavior regarding "unsafe" character in the URL when using the proxy_pass directive: Some of the "unsafe" characters described in RFC1738 ( "These characters are "{", "}", "|", "\", "^", "~", "[", "]", and "`" ") are encoded, some don't, when

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

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 - - [31/Ju

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

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

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 from

handling cookie

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 = ngx_strin

Why 301 permanent redirect with appended slash?

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?

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 (enti

Re: Crash in mail module during SMTP setup

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 SI

Re: Crash in mail module during SMTP setup

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

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

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 ngx_log_debug1(N