Web.config

From Agility
Revision as of 07:30, 31 May 2016 by Artur (Talk | contribs) (Created page with "Category:Configuration Files == Web.config == This file is located within the IIS system immediately beneath the application directory. It contains many settings which ar...")

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Web.config

This file is located within the IIS system immediately beneath the application directory. It contains many settings which are related to the .NET environment which are outside of the scope of this document.

System Name Parameter

<appSettings> Section

The important entry is this section is the system name parameter:-


<?xml version="1.0" encoding="utf-8" ?>

<configuration>

<appSettings>

<add key="SystemName" value="sxp2.1" />

</appSettings>


The “SystemName” parameter is used to locate the configuration file stored in the systems registry under


HKEY_LOCAL_MACHINE\SOFTWARE\SoftSolutions\SXP


There should then be an entry in this location matching the above name. If the Web.config file does not contain a SystemName parameter then “Default” is used instead to search the registry.


The “SystemConfigFilePath” parameter within the system name in the registry should point to the file which contains the full configuration information. The default name for this parameter file is “sxp.Default.config.xml”.

Controlling the size of document size which can be uploaded.

The Web.config file also contains information regarding the maximum size of document which can be uploaded into the database. If these parameters are omitted then there will be a default size of 4 M/B. Both entries should appear within the <system.web> section.


<httpRuntime

maxRequestLength="20000"

enableKernelOutputCache="true"

/>

“MaximumRequestLength” is the maximum upload size on Kilobytes. In this example the limit is 20000 * 1024 bytes( i.e. 20 Megabytes).



<sessionState> Settings

By default ASP.NET uses cookies to identify which requests belong to a particular session. If cookies are not available, a session can be tracked by adding a session identifier to the URL.


To disable cookies, set sessionState cookieless="true", leaving it as “false” enables cookies.


<sessionState

mode="InProc"

stateConnectionString="tcpip=127.0.0.1:42424"

sqlConnectionString="data source=127.0.0.1;Trusted_Connection=yes"

cookieless="false"

timeout="30"

/>