# Http keepalive proxy upstream

**URL:** <https://www.ruby-forum.com/t/http-keepalive-proxy-upstream/191411>\
**Category:** NGINX\
**Created:** [July 12, 2010, 9:58am UTC](https://www.ruby-forum.com/t/http-keepalive-proxy-upstream/191411 "2010-07-12T09:58:55Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Arjan\_Filius](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/a/e495f1/32.png) [@Arjan\_Filius](https://www.ruby-forum.com/u/Arjan_Filius)\
**Post date:** [July 12, 2010, 9:58am UTC](https://www.ruby-forum.com/t/http-keepalive-proxy-upstream/191411/1 "2010-07-12T09:58:55Z")

</div>

Hello nginx mailing-list,

Just entered this email list, after setup nginx as reverse proxy.

Configured nginx (nginx-0.7.67) on ubuntu 10.04LTS 64 bits as  
https → http reverse proxy.

After successfull tests, now i noticed an issue with authenticating with  
ISS. and after some research i found out that it is the  
(missing) http-keepalive to backend is wat breaks authentication.

I found a post of the issue with ISS/keepalives/authentication:

> **[Turing off Http Keep-Alive and using Windows Authentication with IIS: Don't...](https://weblog.west-wind.com/posts/2006/Feb/05/Turing-off-Http-KeepAlive-and-using-Windows-Authentication-with-IIS-Dont-do-it)**
>
> In an attempt to reduce the connections that IIS uses in AJAX debugging scenarios I tried turning off Http Keep-Alives on the server, only to find that it breaks Windows Authentication with IIS.

Which sound not verry promising to switch keepalive of on ISS\>

> From what i read on  
> [Module ngx\_http\_proxy\_module](http://wiki.nginx.org/NginxHttpProxyModule)  
> NginxHttpProxyModule = It is an HTTP/1.0 proxy without the ability for  
> keep-alive requests yet.

Is there any timeline known when that (proxy-upstream) keepalives may  
get  
implemented? Or perhaps other related information available?

Thanks in advance,

Regards,

Arjan Filius

–  
Arjan Filius  
[mailto:removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)
