000031221 - RSA Archer web page generates an unexpected error in the web.config file -HTTP Error 404.15 - Not Found

Document created by RSA Customer Support Employee on Jun 14, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 3Show Document
  • View in full screen mode

Article Content

Article Number000031221
Applies ToRSA Product Set: Archer
Platform: Windows
IssueAn Archer web page generates an unexpected error.  When custom error messages is turned off in the web.config file, the below error occurs:
HTTP Error 404.15 - Not Found
The request filtering module is configured to deny a request where the query string is too long.

User-added image
CauseLength of request exceeds limit configured for IIS
IIS has a limit on the length of requests it will accept from a client browser. 
Example
A values list field contains a very large number of values, and is configured as a values popup.  When a user clicks the control to display the values popup, the error was thrown.
A Fiddler trace is run while the error was reproduced.  The trace reveals a long request of about 4000 characters being sent to the server. The request includes the value IDs for all of the values in the values list.
If IIS is configured to limit requests to less than that number of characters, the above error is thrown.

 
ResolutionThe following two parameters are involved in limiting the length of a request from a client. 
Ambiguity exists in Microsoft documentation about which of these should be adjusted to avoid the HTTP 401.15 error. 
Try adjusting both of them.
MaxQueryStringLength in the system.web/httpRuntine section of the web.config file
MaxQueryString in the RequestFiltering section
Both of these setting default to 2048 characters.  Both can be configured in IIS Manager.
Configure MaxQueryStringLength
  1. In IIS Manager, highlight the Archer web site (or default web site, as the case may be).
  2. In the Features pane, click to open the Configuration Editor.
  3. In the Section dropdown, select system.web/httpRuntime.
  4. Increase the maxQueryStringLenth parameter to a value above that of the request that is causing the error.
  5. Open a command prompt with the Run as Adminstrator option and issue the command IISRESET
Configure MaxQueryString
  1. In IIS Manager, highlight the Archer web site (or default web site, as the case may be).
  2. In the Features pane, click to open Request Filtering.
  3. In the Actions pane, click Edit Feature Settings
  4. Increase the Maximum Query String parameter to a value above that of the request that is causing the error.
  5. Open a command prompt with the Run as Adminstrator option and issue the command IISRESET.

 

Attachments

    Outcomes