# Orbited proxied by nginx hangs web traffic for particular user

**URL:** <https://www.ruby-forum.com/t/orbited-proxied-by-nginx-hangs-web-traffic-for-particular-user/208212>\
**Category:** NGINX\
**Created:** [June 12, 2011, 2:33pm UTC](https://www.ruby-forum.com/t/orbited-proxied-by-nginx-hangs-web-traffic-for-particular-user/208212 "2011-06-12T14:33:38Z")\
**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:** [June 12, 2011, 2:33pm UTC](https://www.ruby-forum.com/t/orbited-proxied-by-nginx-hangs-web-traffic-for-particular-user/208212/1 "2011-06-12T14:33:38Z")

</div>

We are using nginx → Orbited for long-polling, nginx → uwsgi for web  
content (AJAX-driven), and nginx for static files. Problem is, when user  
open more than, dunno, about 6-7 tabs in browser. Then, traffic for user  
(and just for him) just hangs. All new requests takes too long. Is there  
particular config option in nginx or Linux that limits these  
connections? Or there is problem with something else?

Below is our config, server {} section.

listen 192.168.1.1;  
server\_name foo;

client\_max\_body\_size 10m;  
client\_body\_buffer\_size 128k;

access\_log /var/log/nginx/deweloperski.access\_log main;  
error\_log /var/log/nginx/deweloperski.error\_log crit;

keepalive\_timeout 30;

location /poll {

```
proxy_pass http://127.0.0.1:15000/;
proxy_redirect off;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
client_max_body_size 100m;
client_body_buffer_size 128k;
proxy_connect_timeout 90;
proxy_send_timeout 90;
proxy_read_timeout 90;
proxy_buffer_size 4k;
proxy_buffers 4 32k;
proxy_busy_buffers_size 64k;
proxy_temp_file_write_size 64k;

```

}

location /poll/tcp {

```
proxy_pass http://127.0.0.1:15000/tcp;
proxy_buffering off;
tcp_nodelay on;

```

}

location / {

```
uwsgi_pass deweloperski;
add_header Cache-Control no-store;
add_header Vary *;
expires epoch;
include uwsgi.params;
include uwsgi.conf;

```

}

Posted at Nginx Forum:

> **[Orbited proxied by nginx hangs web traffic for particular user](https://forum.nginx.org/read.php?2,206154,206154#msg-206154)**
>
> We are using nginx -\> Orbited for long-polling, nginx -\> uwsgi for web content (AJAX-driven), and nginx for static files. Problem is, when user open more than, dunno, about 6-7 tabs in browser. Then, traffic for user (and just for him) just...

---

<div class="post-metadata">

**Author:** ![Szymon](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/s/34f0e0/32.png) [@Szymon](https://www.ruby-forum.com/u/Szymon)\
**Post date:** [June 12, 2011, 3:00pm UTC](https://www.ruby-forum.com/t/orbited-proxied-by-nginx-hangs-web-traffic-for-particular-user/208212/2 "2011-06-12T15:00:50Z")

</div>

On 12 June 2011 14:33, Szymon [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote:

> We are using nginx → Orbited for long-polling, nginx → uwsgi for web  
> content (AJAX-driven), and nginx for static files. Problem is, when user  
> open more than, dunno, about 6-7 tabs in browser. Then, traffic for user  
> (and just for him) just hangs.

Browsers have very low per-host connection limits. You will need to  
work around this in your application. Subdomains are a good start. But  
the best solution I know of is to use inter-tab communication in your  
application (via cookies) and restrict the long-polling to just one  
tab.

Thomas