We have created a WebApi solution in VS2012, .NET 4.5. All of our GET and PUT methods now work. It is time to turn on the Digest Authentication and get that piece working.
Before Digest Authentication turned on
When we put in the first URL: http://<server>.com:8001/Subject/Xml/20001 in the browser, we get back our xml package exactly as expected.
After Digest Authentication
When we put in the first URL: http://<server>.com:8001/Subject/Xml/20001 in the browser, we get presented with a pop-up dialog box asking for our credentials. This works properly in that if you enter a bad password, it tells you that you screwed up, and then you get to try again. However, when you get it right, you are presented with the following URL:
http://<server>.com:8001/login.aspx?RedirectURL=Subject/Xml/20001 which then generates a 404 error, because my WebApi doesn't have a LoginController, let alone an .aspx file to redirection.
We already have <authentication mode="None"/> in the web.config.
Did we miss a setting in IIS when we turned on Digest Authentication? This is being done with a WebClient call to the api path. Is there a WebClient / WebApi example out there anywhere that can show us what we are missing?
<div></div>Randy