Welcome! Log In Create A New Profile


Re: nginx 1.17.9-1~bionic - 400 error

Maxim Dounin
March 05, 2020 08:22AM

On Wed, Mar 04, 2020 at 08:54:49PM +0100, roland-brieden@web.de wrote:

> Hey Guys.
> After todays update to nginx 1.17.9-1~bionic all my websites crashes
> into 400 error.
> Going back to nginx 1.17.8-1~bionic and all websites works ok.
> What can i do?

First of all, check your error logs. The reason for any 400 error
returned by nginx is logged into error log at the "info" level.

Note though that the "info" level is below the default logging
level, so you may need to adjust your configuration to see
relevant errors. See http://nginx.org/r/error_log for details.

The most likely reason is that 400 errors you see are somehow
related to duplicate Host or Transfer-Encoding, as outlined in

*) Change: now nginx does not allow several "Host" request header lines.

*) Bugfix: nginx ignored additional "Transfer-Encoding" request header

Probably in your configuration requests with duplicate headers are
generated somehow, leading to 400.

Just in case, relevant commits are:


Maxim Dounin
nginx mailing list
Subject Author Posted

nginx 1.17.9-1~bionic - 400 error

rollyb March 04, 2020 02:56PM

Re: nginx 1.17.9-1~bionic - 400 error

Konstantin Pavlov March 05, 2020 02:22AM

Re: nginx 1.17.9-1~bionic - 400 error

Maxim Dounin March 05, 2020 08:22AM

Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 100
Record Number of Users: 6 on February 13, 2018
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready