Thanks Maxim, I've discovered that the configuration in rails systemintegration / production environment was different from development. So, if someone called a URL that wasn't routable, the server responded empty response instead of sending a 404. When I switched the config, the server started to send 404 and Nginx worked correctly. # config/environments/production.rb # Show exception tby djlebersilvestre - Nginx Mailing List - English
Hi, I'm facing a strange problem using Nginx with reverse proxy to a ruby Thin Server. When someone calls an unrouteable path in our Rails App, Nginx launches a 502 - Bad Gateway correctly. When Nginx receives another resquest (just after the 502), that is valid and routeable, it launches directly again a 502 - Bad Gateway without passing the request to the Thin Server (we can check this inby djlebersilvestre - Nginx Mailing List - English