Title: ASP.NET & IIS bad things
Slug: asp-net-amp-iis-bad-things
Date: 2006-05-08 11:40:00
Author: Kartones
Lang: en
Tags: Development, ASP.NET, Troubleshooting
Description: A discussion on the challenges and frustrations encountered with ASP.NET and IIS, including issues with basic authentication, HttpContext differences, and limitations of HttpModules.

 <p>I'm starting to hate some IIS "features".</p>
<p>First it was IIS basic authentication (which you have to do by active
directory whenever you want or not, just because IIS processes it first and then
handles the result to ASP.NET). I'll search for the MSDN article where this is
explained.</p>
<p>And now, look at the differences between a HttpContext of an ASPX page and
one from a html page (generally speaking, a static resource):</p><p><img src="https://images.kartones.net/posts/screenshots/aspx_handler.jpg" title="ASP.NET Handler" alt="ASP.NET Handler" height="328" border="0" width="406"> <img src="https://images.kartones.net/posts/screenshots/html_handler.jpg" title="HTML Handler" alt="HTML Handler" height="336" border="0" width="361"><br></p><p>Fantastic, no SessionSate! This means that if you're developing a HttpModule
that needs to access Session data, forget all non-dynamic resources...</p>
<p>HttpModules are very cool because with few lines of code you get ISAPI-like
results, but seems they have their limitations too.</p>