Databases
StackOverflow2013
Postsdbo
PORails Application on Nginx and Thin, 400 Bad Request Request Header Or Cookie Too Large
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PORails Application on Nginx and Thin, 400 Bad Request Request Header Or Cookie Too Large
    primarykey
    data
    text
    <p>Static page is served correctly you can visit : <a href="http://www.ec2.lankenow.info/" rel="nofollow">http://www.ec2.lankenow.info/</a> click on the image and it will take you to the error page.</p> <p>Nginx error log:</p> <pre><code>2012/03/16 01:58:41 [alert] 884#0: 768 worker_connections are not enough 2012/03/16 01:58:41 [error] 887#0: *3900 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 23.21.141.105, server: www.ec2.lankenow.info, request: "GET /leads HTTP/1.0", upstream: "http://23.21.141.105:80/leads", host: "www.ec2.lankenow.info", referrer: "http://www.ec2.lankenow.info/" </code></pre> <p>I think I might have to set client_header_buffer_size but dont know how or which file to edit. Any direction how to go about it would be much appreciated.</p> <p><strong>EDIT: This can be added to the http section of nginx.conf which can be found in /etc/nginx/ or usr/local/nginx/ depending on your installation</strong></p> <p>Config file under /etc/nginx/sites-available/</p> <pre><code>upstream vdiamond { server 0.0.0.0:3000; server 0.0.0.0:3001; server 0.0.0.0:3002; } server { listen 80; server_name www.ec2.lankenow.info; access_log /home/ubuntu/vdiamond/log/access.log; error_log /home/ubuntu/vdiamond/log/error.log; root /home/ubuntu/vdiamond/public/; index index.html; location / { # Add expires header for static content location ~* \.(js|css|jpg|jpeg|gif|png)$ { if (-f $request_filename) { expires max; break; } } proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header Host $http_host; proxy_read_timeout 300; proxy_next_upstream off; #proxy_redirect false; if (-f $request_filename/index.html) { rewrite (.*) $1/index.html break; } if (-f $request_filename.html) { rewrite (.*) $1.html break; } if (!-f $request_filename) { proxy_pass http://www.ec2.lankenow.info; break; } } } </code></pre>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USBrad Koch
    1. USsunny31
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PORails Application on Nginx and Thin, 400 Bad Request Request Header Or Cookie Too Large
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PORails Application on Nginx and Thin, 400 Bad Request Request Header Or Cookie Too Large
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PORails Application on Nginx and Thin, 400 Bad Request Request Header Or Cookie Too Large
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI'm going to guess that the `worker_connections` is more likely the issue -- or, rather, the symptom -- why so many workers? Are there mistakes in your application that keep workers from being reaped or that too-easily spawns new workers?
      singulars
      1. PORails Application on Nginx and Thin, 400 Bad Request Request Header Or Cookie Too Large
      1. USsarnold
    2. COSorry, its not my app but managing someone else app code. I am just trying to set up test server so eventually I can fix the app.
      singulars
      1. PORails Application on Nginx and Thin, 400 Bad Request Request Header Or Cookie Too Large
      1. USsunny31
    3. COHave you tried increasing worker_connections and workers?
      singulars
      1. PORails Application on Nginx and Thin, 400 Bad Request Request Header Or Cookie Too Large
      1. USGareth Davies
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload