Okay, that works on my local VS2008 server, but not on our dev server. If I paste the following into my browser, it logs me right into my local copy and redirects to the default.aspx page...
If I feed this same URL to the 3rd party site downloader, it also logs in and starts downloading the site with no problem.
Likewise, if I paste the following into my browser, it logs me into our development server copy and redirects to the default.aspx page...
Unfortunately, when I use this same URL in the site downloader, it receives this error from the web server...
"Unauthorized" (401) at link devserver:200/publicLogin.aspx?u=username&p=password&ReturnUrl=/Default.aspx
The tool is running under my user credentials (the same as the browser), and they're both using the same username and password to authenticate to the Sitefinity site. Again, both methods work fine on my local copy (which uses the same database and content as our development server).
Is there a difference in the way VS2008's development server handles authentication versus how IIS6.0 handles it? Is there something in the login code or web.config I could change to treat the servers differently?