5.2.4 Points to be considered during Web server integration
This section explains the points to be considered when integrating with the Web server.
- Organization of this subsection
(1) Upper limit value of the request headers and response headers that can be sent and received by the Web container
When integrating with the Web server, an upper limit is set on the size of the request headers and the response headers that can be sent and received by the Web container. The respective upper-limit value is 16 KB. Note that you cannot send and receive the headers exceeding 16 KB.
(2) Points to be considered when using Cosminexus HTTP Server
You cannot use the virtual host functionality of the HTTP Server when a Web server is integrated.
To perform different redirections for each virtual host, use the management portal or Smart Composer to build multiple HTTP Servers on the same host, and then set a redirector for each HTTP Server.
(3) Points to be considered when using the Microsoft IIS
The points to be considered when using the Microsoft IIS are explained below:
-
When multiple Web sites are built by Microsoft IIS, you cannot integrate simultaneously with these Web sites. When you are building multiple Web sites, set a redirector in each Web site.
-
Change the URL information for the requests transferred to the Web container with the redirector for Microsoft IIS. Use the changed request URL in the ISAPI filter.
Consequently, you cannot acquire the request URL received first by the Microsoft IIS with the ISAPI filter executed after the redirector for Microsoft IIS. If you want to acquire the request URL received by Microsoft IIS with the ISAPI filter, you need to set a higher priority order for the ISAPI filter as compared to the redirector for Microsoft IIS. Note that when you need to change the priority order of the redirector for Microsoft IIS to Medium or Low in order to adjust the priority order of the ISAPI filter, specify the priority order with the filter_priority key of the action definition file of the redirector for Microsoft IIS. For the filter_priority key, see 14.2.1 isapi_redirect.conf (Redirector action definition file for Microsoft IIS).
-
When integrating with Microsoft IIS, even if you specify the following HTTP request headers in the Web client, you cannot receive these request headers in a Web application:
-
tomcaturl
-
tomcatquery
-
tomcatworker
-
tomcattranslate
These HTTP request headers are used in the redirector.
-
-
When integrating with Microsoft IIS, you cannot specify settings for distributing requests by the POST data size.