(Not Related to a Specific Release) - ...
<location path="cms"> element
The cms virtual directory (which should have been configured within IIS) needs its own configuration section within the web.config.
This section defines the http handler(s) and module(s) to be used for the cms manager, as well as authorization and authentication settings.
Notice when using an Outscaling configuration including two or more Cms instances, you need to enable an extra http handler for Outscaling's external webservice handling. This http handler mapping must appear first within the list of httpHandlers, since the other http handler mapping uses a wildcard mapping.
Example
XML |
Copy Code
|
<location path="cms">
<system.web>
<globalization requestEncoding="iso-8859-1"/>
<authentication mode="None">
</authentication>
<authorization>
<!-- allow access for all users, the manager uses it's own implementation for authenticating users -->
<allow users="*"/>
</authorization>
<httpModules>
<!-- clear the inherited httpModules -->
<clear/>
<!-- add SessionStateModule to (re-)enable session support -->
<add name="Session" type="System.Web.SessionState.SessionStateModule"/>
</httpModules>
<httpHandlers>
<!--clear the inherited httpHandlers-->
<clear/>
<!-- add http handler for Outscaling's external webservice
(only needed when Outscaling is needed between two or more Cms instances) -->
<!-- <add verb="*" path="/cms/webservice.dws" type="Smartsite.Interop.IIS.WebserviceHandler,Smartsite.Interop"/> -->
<!-- add http handler for cms manager -->
<add verb="*" path="/cms/*.dws" type="Smartsite.Interop.IIS.Handler,Smartsite.Interop"/>
</httpHandlers>
</system.web>
</location>
|
Attributes
None.
Parent element
Element name |
Description |
<configuration> |
Root element of the web.config file. |
Child elements
None.