I have a reverse proxy implemented using a HTTP handler. The handler handles all trafic (using webrequest) between my ASP.NET application and a remote ASP.NET application. To be able to call the remote site, I have to add some HTTP headers and a client certificate. So far so good.

When I test this on the VS 2005 webserver (Cassini), everything works great! (it really does :-) )

But now I moved it to IIS6 and the remote site now returns that I cannot be authenticated. Somehow IIS does something with the request or headers that the Cassini webserver doesn't, because they both run exactly the same code.

Can someone help me with this or maybe a workarround?

 Thanks!

Greyfox.

Fixed.

The Cassini webserver uses certificates from the current user store and the site in IIS runs under a system account so it reads from the local computer store.

An error in one of the certificate stores solved the problem.