3

Closed

Reverse Proxy Doesn't Handle Basic HTTP Authentication

description

I setup version 3.5 as a reverse proxy, it works well with normal websites in backend server, but it can't handle the ones request authentication (HTTP authentication). The symptom is:

Proxy server: http://www.myproxy.com

Backend server: http://192.168.1.10

When I use internet browser access http://www.myproxy.com, the browser prompted the login box, I fill in the correct login name and password, it prompted to login again. I checked the HTTP log of the backend webserver, the status code is 401 Unauthorized.

The following are the configuration ManagedFusion.Rewriter

ManagedFusion.Rewriter:

RewriteEngine OnRewriteRule ^(.*) http://192.168.1.11$1 [P]

Both proxy and backend servers are Windows 2003 IIS6 with ASP.NET 2.0
Closed Aug 13, 2010 at 7:28 PM by
Fixed in 3.5.3

comments

daern wrote May 18, 2010 at 3:13 PM

I see the same thing here. Very interesting in the outcome of this...

nberardi wrote May 18, 2010 at 4:37 PM

Just to be clear we are talking about Basic HTTP Authentication. As described here: http://en.wikipedia.org/wiki/Basic_access_authentication Because I know from past experience that Windows and LDAP authentication isn't going to work. And I don't have enough resources to dedicate to figuring it out.

ixquisite wrote Aug 7, 2010 at 2:37 AM

Yes, definitely support this one - would be great to have! Might be important to mention that basic and encrypted (digest) - if that makes a difference - would be great to be supported. I am a complete novice here.