# Nginx living behind Amazon LoadBalancer reporting large number of 400 Bad Requests

**URL:** <https://www.ruby-forum.com/t/nginx-living-behind-amazon-loadbalancer-reporting-large-number-of-400-bad-requests/205792>\
**Category:** NGINX\
**Created:** [April 15, 2011, 6:41pm UTC](https://www.ruby-forum.com/t/nginx-living-behind-amazon-loadbalancer-reporting-large-number-of-400-bad-requests/205792 "2011-04-15T18:41:43Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![dubstep](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/cdc98d/32.png) [@dubstep](https://www.ruby-forum.com/u/dubstep)\
**Post date:** [April 15, 2011, 6:41pm UTC](https://www.ruby-forum.com/t/nginx-living-behind-amazon-loadbalancer-reporting-large-number-of-400-bad-requests/205792/1 "2011-04-15T18:41:43Z")

</div>

I have a set of Amazon EC2 servers living behind one of the Amazon  
elastic load balancers. For some reason one set is reporting a large  
number of 400 Bad Request messages that appear to originate with the  
load balancer. Traffic can still come in and out just fine but this is  
concerning me. Was wondering if anyone has seen this with Nginx or with  
Amazon cloud stuff before. Cannot seem to find any references to it out  
there. Mainly, I am trying to nail it down to either a Nginx problem or  
an Amazon problem so I can get this solved.  
I have tried the only mention to 400 error problems which was adding  
“large\_client\_header\_buffers 4 8k” to my default config file but has not  
made any difference.

Thanks,  
Brian

Posted at Nginx Forum:

> **[Nginx living behind Amazon LoadBalancer reporting large number of 400 Bad...](https://forum.nginx.org/read.php?2,191550,191550#msg-191550)**
>
> I have a set of Amazon EC2 servers living behind one of the Amazon elastic load balancers. For some reason one set is reporting a large number of 400 Bad Request messages that appear to originate with the load balancer. Traffic can still come in and...

---

<div class="post-metadata">

**Author:** ![bindsocket](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/b/898d66/32.png) [@bindsocket](https://www.ruby-forum.com/u/bindsocket)\
**Post date:** [April 16, 2011, 1:31pm UTC](https://www.ruby-forum.com/t/nginx-living-behind-amazon-loadbalancer-reporting-large-number-of-400-bad-requests/205792/2 "2011-04-16T13:31:16Z")

</div>

Hey,  
it’s Amazon’s problem. 400 errors mean that the other side connected,  
but  
didn’t send HTTP request. This is common behavior among dumb load  
balancers  
that only check if port is open and not if web server really works.

Best regards,  
Piotr S. \< removed\_email\_address@domain.invalid \>