4.9.4 Notes
-
If a client denies reception of a cookie, the cookie is not sent back to the server, so the functionality of 4.9.2(2) Session management using cookies is disabled.
-
For a KeepAlive connection the determination process is executed only when processing the first request after connection, and the determination process is not executed from the second request onwards in the same connection. If the request of flow-restriction settings differs with the request that is connected initially, the server does not determine the request from second request onwards.
-
The message sent when request is denied by flow-restricting functionality will not change even if you specify the ErrorDocument directive. Also, the Redirect directive and RedirectMatch directive are executed after mod_hws_qos module control determines that processing can continue.
-
If the server simultaneously receives requests that exceed number of settings of QOSRejectionServers directive, the server may not deny the requests correctly even if you use the flow-restriction functionality. If a HTML file specified in QOSResponse directive contains a link such as image data link, the server accesses again to fetch the image data. This access also becomes the target of flow-restriction process, and you may not obtain the image data. Be careful to set the proper link when you create HTML file.
-
Setting of HWSErrorDocumentMETACharset directive is valid in Windows version for the character set of error document.
-
You must set another name in QOSCookieName directive if you set the session management in which cookie is used for each URL, or for VirtualHost.
-
Set the QOSCookieServers directive and QOSRejectionServers directive after setting the number of server processes (set in the ThreadsPerChild directive or MaxClients directive). If you set the QOSCookieServers directive and QOSRejectionServers directive before setting the number of server processes, the server may not start.