8.10.2. Internet Information Services

8.10.2.1. 32-bit web server extension version on a IIS 64-bit version

If you are using the 32-bit version of a web server extension on a 64-bit version of the operating system, you must indicate to the web server that it can run 32-bit applications. To do this, you must perform the following operations:

For IIS 5.1, IIS 6.0, start the command interpreter and run the following command in it:

cscript %SYSTEMDRIVE%\inetpub\adminscripts\adsutil.vbs SET W3SVC/AppPools/Enable32bitAppOnWin64 1

For IIS 7.0 or later, open the dialog box to configure the main application pool settings: IIS configuration manager – <Specific server> – Application pools – <Desired application pool> – Advanced parameters. Set parameter Allow 32-bit applications to True .

8.10.2.2. Application pool settings

When configuring IIS, remember that within one application pool, more than one web server extension module cannot be executed which differ only in the third and fourth digits of the version. To organize such operation, number if the application pools equal to the number of different versions of extension modules, and manually bind each virtual application of the web client to the required application pool.

If the publication serves a file version of the infobase, it is not recommended that you allow the web server to create several working processes in the same application pool. If in the infobase file mode background jobs are used, for correct operation purposes the number of working processes in the pool you use must be equal to 1. Working process numbers is managed by the following parameter: IIS configuration manager – <Specific server> – Application pools – <Desired application pool> – Advanced parameters – Working processes maximum number (in the Process model parameter group).

8.10.2.3. Error presentation setup

If 1C:Enterprise errors (when using IIS web server version 7.x and later) are displayed with a text of the following type: 500, an internal server error. Problem with requested resource; the resource cannot be displayed, you must change the parameter that controls the presentation of errors. To do this, open the dialog box to configure error page parameters: IIS configuration manager – <Specific server> – websites – <Default Web Site> – <Virtual application name> – Error pages – Change parameters… In the opened dialog box, set the If the server detects an error, return parameter to Detailed error messages. Then, click OK.

8.10.2.4. Setup of the URL permissible length

When accessing the standard OData interface, the URL can be of significant length. By default, IIS restricts URL length to 260 characters. To change this restriction, it is necessary (with administrator rights) in the system registry, in the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HTTP\Parameters section, create a UrlSegmentMaxLength parameter of DWORD type. Set this parameter to a required value or to 0 for unlimited URL length. Then, restart the computer on which the IIS is installed.

8.10.2.5. HTTPS-connection setup

In some cases, when downloading large amounts of data over an HTTPS connection (when using the IIS web server) errors may occur. In these cases, try to use TLS 1.2 or TLS 1.1 protocol. For IIS 7.5 and later (Windows Server 2008 R2, Windows 7 and later), it is possible to enable the use of TLS 1.1 and later protocols. To do this, follow these steps:

in the system registry, in the section HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.1\Server create DisableByDefault parameter of DWORD type and set its value to 0.
in the system registry, in the section HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Server create DisableByDefault parameter of DWORD type and set its value to 0.
These actions should be performed on behalf of a user with the administrative rights.

Then, restart the computer on which the IIS is installed.

8.10.2.6. Updating client application

To update the client application, set one of the following MIME types for .zip extension: application/x-zip-compressed (IIS web server is configured by default) or application/zip (IANA recommendation).

To set (or check) a MIME type, do the following:

Entire web server settings: IIS configuration manager – IIS group – MIME types.
Website settings: IIS configuration manager – websites – <selected website> – IIS group – MIME types.
Website page settings: IIS configuration manager – websites – <selected website> – <selected web page> – IIS group – MIME types.
MIME types list: find a record for .zip extension and check whether the specified MIME type is supported by 1C:Enterprise. If the list does not contain a record for .zip extension, create this record.

8.10.2.7. Embedding Web Client

If you need to embed a web client into a website, it is recommended that you configure the X-Frame-Options response header for the web client application as follows:

If an external website and a web client are published on a single web server, the header accepts sameorigin.
If an external website and a web client are published on different web servers, the header is set to allow-from %WebSite%. In this expression, %WebSite% refers to a URL (protocol, domain, and port) of an external website where you plan to use the embedded web client.
If a web client cannot be integrated with an external web site, the header accepts deny.

If there is no need to configure the response header, make sure that the web client application settings do not contain X-Frame-Options response header with the deny value.