M
Mark Rae
Hi,
I'm presently upgrading a v1.1 ASP.NET app to v2. Parts of site run under
SSL and parts don't, and the site uses this code:
http://www.codeproject.com/aspnet/WebPageSecurity.asp
to switch between them - works perfectly.
Setting up which files and/or folders need to run under https is a simple
matter of adding some web.config settings. The code appears to run perfectly
well under v2, but gives lots of warnings when the site is compiled. The
relevant settings in web.config are as follows:
<?xml version="1.0"?>
<configuration>
<configSections>
<section name="secureWebPages"
type="Hyper.Web.Security.SecureWebPageSectionHandler, WebPageSecurity"
allowLocation="false"/>
</configSections>
<secureWebPages>
<directory path="security"/>
</secureWebPages>
<system.web>
<httpModules>
<add name="SecureWebPage"
type="Hyper.Web.Security.SecureWebPageModule, WebPageSecurity"/>
</httpModules>
</system.web>
</configuration>
The warnings messages are:
Could not find schema information for the element 'secureWebPages'.
Could not find schema information for the element 'directory'.
Could not find schema information for the attribute 'path'.
As I said, the assembly appears to work perfectly under v2 of the Framework,
so:
1) Do I need to be concerned about the warning messages?
2) Is there a way to specify the settings in web.config which the assembly
needs which will not generate the warning messages?
3) There doesn't appear to be a v2 version of the assembly available, but is
there a "native" v2 way of achieving the same functionality?
Any assistance gratefully received.
Mark
I'm presently upgrading a v1.1 ASP.NET app to v2. Parts of site run under
SSL and parts don't, and the site uses this code:
http://www.codeproject.com/aspnet/WebPageSecurity.asp
to switch between them - works perfectly.
Setting up which files and/or folders need to run under https is a simple
matter of adding some web.config settings. The code appears to run perfectly
well under v2, but gives lots of warnings when the site is compiled. The
relevant settings in web.config are as follows:
<?xml version="1.0"?>
<configuration>
<configSections>
<section name="secureWebPages"
type="Hyper.Web.Security.SecureWebPageSectionHandler, WebPageSecurity"
allowLocation="false"/>
</configSections>
<secureWebPages>
<directory path="security"/>
</secureWebPages>
<system.web>
<httpModules>
<add name="SecureWebPage"
type="Hyper.Web.Security.SecureWebPageModule, WebPageSecurity"/>
</httpModules>
</system.web>
</configuration>
The warnings messages are:
Could not find schema information for the element 'secureWebPages'.
Could not find schema information for the element 'directory'.
Could not find schema information for the attribute 'path'.
As I said, the assembly appears to work perfectly under v2 of the Framework,
so:
1) Do I need to be concerned about the warning messages?
2) Is there a way to specify the settings in web.config which the assembly
needs which will not generate the warning messages?
3) There doesn't appear to be a v2 version of the assembly available, but is
there a "native" v2 way of achieving the same functionality?
Any assistance gratefully received.
Mark