Altairis Web Management Toolkit
solves several common problems often seen in web applications in production:
Errors happen. It's good idea to be informed when your application crashes. It's even better idea to get all the relevant data, which will allow you to find out
the error happened. There are complex and powerfull solutions, like ELMAH. But I don't trust ELMAH, since the library is so complex, that by definition must contain its own share of bugs. Also its customization takes maybe more time and effort
than writing simpler module.
Displaying error message in ASP.NET and IIS is trickier that it seems. There are two separate error page mechanisms (one in IIS and one in ASP.NET) and getting the second one to work properly (including returning the proper HTTP status code) is quite tricky.
This library contains unified error handling for IIS and ASP.NET errors.
Canonical host name redirection
Web sites often have more than one host name, ie. your-company.com
. For many reasons (including SEO and caching) it's recommended to have single main canonical host name and all other domains as aliasses. It's possible to use the URL Rewrite module in IIS, but you can't switch it off
for local requests and it may not be available in some scenarios. HostRedirector comes here to the rescue.
Switching between HTTP and HTTPS automatically
Common HTTP does not offer any protection of the communication. Server identity could not be validated and transferred data are not protected from eavesdropping and malicious modifications. HTTPS (or SSL, TLS) does solve this problem, but brings is own family
of them: caching, higher CPU usage and so on. For most applications, the recommended solution is to use HTTPS only when needed - ie. for login pages and pages containing sensitive data. SSL redirector contained in this library solves this problem. You can
specify areas of your web site, where SSL is mandatory (or prohibited) and the module would automatically redirect requests between secure and open connection.
All these features are "developer friendly". Usually they're needed only un production web sites, not when developing on localhost. All the functionality is turned off by default for local request, so you can have single configuration for development
and production servers.