# HTTP/1.1 backend

**URL:** <https://www.ruby-forum.com/t/http-1-1-backend/198025>\
**Category:** NGINX\
**Created:** [October 25, 2010, 8:02am UTC](https://www.ruby-forum.com/t/http-1-1-backend/198025 "2010-10-25T08:02:57Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Dobai-Pataky\_BSSSSl](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/77aa72/32.png) [@Dobai-Pataky\_BSSSSl](https://www.ruby-forum.com/u/Dobai-Pataky_BSSSSl)\
**Post date:** [October 25, 2010, 8:02am UTC](https://www.ruby-forum.com/t/http-1-1-backend/198025/1 "2010-10-25T08:02:57Z")

</div>

Has anyone here had any luck using a 2 layer proxy system to provide  
keep-alive support to nignx’s backend.

My goal is to setup a system like this:  
User -\> Nginx -\> SoftwareX -\> Backend (Different Country) -\> SoftwareX  
-\>  
Nginx -\>User  
So in other words another layer.

Ive done some research and found perlbal and vicompress. Any other  
software  
that supports a HTTP/1.1 backend pool (keep alive) that you know of? Any  
recomendations?

Oh and BTW to anyone who says that it wont matter, it will, it will  
remove  
the need for a round trip in the proxy process (19ms), big saving.

---

<div class="post-metadata">

**Author:** ![casper\_the\_ghost](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/58956e/32.png) [@casper\_the\_ghost](https://www.ruby-forum.com/u/casper_the_ghost)\
**Post date:** [October 25, 2010, 6:59pm UTC](https://www.ruby-forum.com/t/http-1-1-backend/198025/2 "2010-10-25T18:59:04Z")

</div>

On Mon, Oct 25, 2010 at 1:01 AM, SplitIce [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote:

> recomendations?
> 
> Oh and BTW to anyone who says that it wont matter, it will, it will remove  
> the need for a round trip in the proxy process (19ms), big saving.

I think Apache Traffic Server may do what you need:

> **[Apache Traffic Server](https://trafficserver.apache.org/)**

–  
RPM

---

<div class="post-metadata">

**Author:** ![casper\_the\_ghost](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/58956e/32.png) [@casper\_the\_ghost](https://www.ruby-forum.com/u/casper_the_ghost)\
**Post date:** [October 26, 2010, 4:45am UTC](https://www.ruby-forum.com/t/http-1-1-backend/198025/3 "2010-10-26T04:45:49Z")

</div>

Indeed I found that in my research but I cant find any real  
documentation on  
its keep alive system/backend pooling. This leads me to beleive it just  
fowards the keep alive onto the backend server, which is not preferable.  
Any  
ideas?

---

<div class="post-metadata">

**Author:** ![casper\_the\_ghost](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/58956e/32.png) [@casper\_the\_ghost](https://www.ruby-forum.com/u/casper_the_ghost)\
**Post date:** [October 26, 2010, 8:16am UTC](https://www.ruby-forum.com/t/http-1-1-backend/198025/4 "2010-10-26T08:16:39Z")

</div>

In case you didnt read the previous post in the thread my email was in  
reguards to apache traffic server and not in reguards to nginx (I know  
it  
doesnt not support HTTP/1.1) I am looking for a intermediary between the  
two  
to use to reduce round packet trips/delay.

Candidates so far:  
ViCompress (has connection pool support, C, event based), PerlBal (has  
connection pool support, Perl, event based), Apache Traffic Server  
(connection pool support???, C?, event based)

Of course it would be preferable that nginx have HTTP/1.1 support but I  
dont  
see that happening soon.

---

<div class="post-metadata">

**Author:** ![casper\_the\_ghost](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/58956e/32.png) [@casper\_the\_ghost](https://www.ruby-forum.com/u/casper_the_ghost)\
**Post date:** [October 26, 2010, 4:52am UTC](https://www.ruby-forum.com/t/http-1-1-backend/198025/5 "2010-10-26T04:52:05Z")

</div>

SplitIce at 2010-10-26 10:44 wrote:

> Indeed I found that in my research but I cant find any real  
> documentation on its keep alive system/backend pooling. This leads me  
> to beleive it just fowards the keep alive onto the backend server,  
> which is not preferable. Any ideas?  
> No，it’s not supported yet.

–  
Weibin Y.
