Web.Config should include the following variables in order for the HTTP Prefix Module to run,
If no variables added then the module will not run and HTTPPrefixModule will be set to "false".
STEP 1 : Add the following entries in the "<appSettings>" section of "<configuration>"
<!-- MicroMighty SDK : HTTPPrefixModule Variables -->
<add key="HTTPPrefixActive" value="true" />
<add key="HTTPPrefixCommaSeparatedExcludedExtensions" value="" />
<add key="HTTPPrefixCommaSeparatedSSLPathAndFileNames" value="PaymentPage.aspx" />
<add key="HTTPPrefixEnforcePrefixInAddress" value="false" />
<add key="HTTPPrefixEnforceNoPrefixInAddress" value="true" />
<add key="HTTPPrefixHostPrefix" value="www." />
<add key="HTTPPrefixTestModeOnly" value="false" />
STEP 2 : Add the following entries in the "<httpModules>" section of "<system.web>"
<!-- Register HTTP modules for IIS 6.0 and IIS 7.0 running in Classic mode -->
<add name="HTTPPrefixModule" type="MicroMighty.SDK.Web.HttpModules.HTTPPrefixModule" />
STEP 3 : Add the following entries in the "<modules>" section of "<system.webServer>"
<!-- Register HTTP modules for IIS 7.0 running in Integrated mode -->
<add name="HTTPPrefixModule" type="MicroMighty.SDK.Web.HttpModules.HTTPPrefixModule" />
Depends on your IIS settings - you may need to enforce HTTP modules on HTML and maybe other files,
By default ASPX files are processed through the ASP.NET pipeline, however, you may need to configure IIS to
route HTML files (and maybe other files) through the
ASP.NET pipeline or move to
IIS Integrated Mode.