This has been fixed and it wasn't nginx's issue at all! We were using a nodejs framework which reads a header and responds with 303 or 302. This app was incorrectly reading the header. http2 implies headers will be in lowercase and this app was reading the header in mixed/title case. The reason it completely missed me was because I tested by copying the request as a curl command from browsby ishanjain - Nginx Mailing List - English
Hey! I am currently using nginx 1.23(also tested with nginx 1.22). I am using nginx as a reverse proxy for an application. It responds to a PUT request with 303 status code(303 See Other). Nginx is rewriting this to 302. This causes problems since 302 and 303 have completely different semantics. I found this old thread https://forum.nginx.org/read.php?2,278217,278223#msg-278223 where some oby ishanjain - Nginx Mailing List - English
![]() |
![]() |
![]() |
![]() |
![]() |