Sometimes NGINX returns 405 on POST, when 504 GATEWAY TIMEOUT is expected

Hey, yesterday I had a situation where NGINX *sometimes under some configurations* returned a 405 METHOD NOT ALLOWED, when it was supposed to return a 504 GATEWAY TIMEOUT. Since troubleshooting this took a while, and information that I found was fragmented, outdated, or inaccurate, I wrote a blog

Re: Same cached objects, but different body_bytes_sent

I can imagine a client only asking for the first 2xx bytes (where a 206 reply is not required) to compare against its local cache. Posted at Nginx Forum: https://forum.nginx.org/read.php?2,274589,274622#msg-274622 ___ nginx mailing list nginx@nginx.org

Re: Same cached objects, but different body_bytes_sent

@itpp2012: I cant replicate the problem using curl from 2 different locations. Its not supposed to return 206 in range requests? @zhang_chao: I'm not sure about this, but its not supposed to return 499 in this case? Tks, Guilherme On Fri, Jun 2, 2017 at 3:45 AM, Zhang Chao wrote: > Hi! > >

Re: Help! backend tomcat server tries to perform Web Sockets handshake (HTTP 101) but Nginx never returns a response back to the client

Fixed. Had to replace the Classic AWS ELB with an ALB. Posted at Nginx Forum: https://forum.nginx.org/read.php?2,274580,274615#msg-274615 ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx