Version 3.5 Reverse Proxy Seems Can't Handle HTTP Authentication

May 15, 2010 at 8:29 AM
Edited May 15, 2010 at 3:40 PM

Dear all professionals,

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:

Backend server:

When I use internet browser access, 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


RewriteEngine On
RewriteRule ^(.*)$1 [P]

Both proxy and backend servers are Windows 2003 IIS6 with ASP.NET 2.0

Does I do something wrong?

Best regards,


May 17, 2010 at 7:53 PM
This discussion has been copied to a work item. Click here to go to the work item and continue the discussion.
May 18, 2010 at 5:39 PM

Just to be clear we are talking about Basic HTTP Authentication.  As described here:

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.