Thank you for the contribution, Sam.
This is the extension of the
IHttpModule application difference between IIS default setup and UltiDev Cassini.
You are right, UltiDev Cassini applies forms auth to all resources, not only to ASPX and ASMX. The reason for that is that in Cassini all registered IHttpModule derivatives (and forms auth is just one of them) get a chance to handle every requests that comes through, regardless whether the request is for ASPX or for a generic resource, like JPEG. In IIS default settings ensure that only native ASP.NET resources are handled by ASP.NET ISAPI - the rest, like JPEGs, CSS, etc. are handled by IIS itself. This approach, while it yields better performance, has also its drawbacks, like "404 not found" error for .ASPX are handled by your code, and 404s for JPEGs are handled by IIS, returning potentially inconsistent error pages between the two. To eliminate this gap many developers and Ops configure IIS to pass all requests through ASP.NET filter. If they do that, you are likely to see exactly the same issue you see with Cassini.
The bottom line, Sam, is configuring authentication the way you did it will not only make it working for Cassini, but will also make it work for IIS when all requests are configured to go through ASP.NET ISAPI.
(We are sorry if this explanation is a bit convoluted - it's a pretty advanced topic and it's kind of hard to lay it out in a few sentences).
Best regards,
UltiDev Team.
Please donate at
http://www.ultidev.com/products/Donate.aspx to help us improve our products.