Re: Crash in mail module during SMTP setup

2019-07-31 Thread Rob N ★
On Wed, 31 Jul 2019, at 2:11 AM, Maxim Dounin wrote: > > I think I see the problem - when using SMTP with SSL and resolver, > > read events might be enabled during address resolving, leading to > > duplicate ngx_mail_ssl_handshake_handler() calls if something > > arrives from the client, and

Re: Why 301 permanent redirect with appended slash?

2019-07-31 Thread J. Lewis Muir
On 07/31, Francis Daly wrote: > On Tue, Jul 30, 2019 at 05:12:01PM -0500, J. Lewis Muir wrote: > > Hi there, > > > 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

Setting Charset on Nginx PHP virtual host

2019-07-31 Thread Vincent M.
Hello, I tried to set the Charset of a virtual host like this: server {     root /var/www/mywebsite.com; ...     charset iso-8859-1;     override_charset on; ...     location ~ \.php$ {     include snippets/fastcgi-php.conf;     fastcgi_pass

Re: zero size buf in writer in 1.17.2

2019-07-31 Thread Maxim Dounin
Hello! On Tue, Jul 30, 2019 at 01:23:26PM +0200, Witold Filipczyk wrote: > 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

[nginx] Gzip: fixed "zero size buf" alerts after ac5a741d39cf.

2019-07-31 Thread Maxim Dounin
details: https://hg.nginx.org/nginx/rev/0ef2bc0ec9c9 branches: changeset: 7545:0ef2bc0ec9c9 user: Maxim Dounin date: Wed Jul 31 17:29:00 2019 +0300 description: Gzip: fixed "zero size buf" alerts after ac5a741d39cf. After ac5a741d39cf it is now possible that after zstream.avail_out

[nginx] Version bump.

2019-07-31 Thread Maxim Dounin
details: https://hg.nginx.org/nginx/rev/e1a3fa4c054f branches: changeset: 7544:e1a3fa4c054f user: Maxim Dounin date: Wed Jul 31 17:28:41 2019 +0300 description: Version bump. diffstat: src/core/nginx.h | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diffs (14 lines):

Re: Why 301 permanent redirect with appended slash?

2019-07-31 Thread Francis Daly
On Tue, Jul 30, 2019 at 05:12:01PM -0500, J. Lewis Muir wrote: Hi there, > 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

Re: Implicit root location?

2019-07-31 Thread Francis Daly
On Tue, Jul 30, 2019 at 04:20:41PM -0500, J. Lewis Muir wrote: Hi there, > 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 >

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

2019-07-31 Thread mightbeanyone
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