4.3.2 update broke devise authenticated root route

[CrazybutSolid]

Apologies for the lack of details, not an advanced programmer.

Describe the bug
Updated from Puma 4.3.1 to 4.3.2

After the update, when signing up or signing into my website, puma would always take me to the unauthenticated root.

Downgraded to 4.3.1 and everything is fine again.

Puma config:

Puma 4.3.2

run lambda { |env| [200, {"Content-Type" => "text/plain"}, ["Hello World"]] }

Run it with:

bundle exec puma -C <where_your_config_is> hello.ru

If you cannot reproduce with a hello world application or other simple application, we will have a lot more difficulty helping you fix your issue, because it may be application-specific and not a bug in Puma at all.

There is also a Dockerfile available for reproducing Linux-specific issues. To use:

$ docker build -f tools/docker/Dockerfile -t puma .
$ docker run -p 9292:9292 -it puma

This will help you to create a container that reproduces your issue.

Expected behavior
A clear and concise description of what you expected to happen.

Desktop (please complete the following information):

• OS: [e.g. Mac, Linux]
• Puma Version [e.g. 4.1.1]

[nateberkopec]

Duplicate of #2132, please upgrade to 4.3.3.

[ccasabona]

Puma 4.3.2 also broke our login redirect (not using devise). Puma 4.3.3 came through while writing this post. This version is working correctly.