Question & Answer
Question
Here is the description for max-client-read in webseald-<instance name>.conf:
```
# This parameter specifies the maximum number of bytes that
# WebSEAL will read from a client when parsing an HTTP request.
# The total size of the URL and HTTP headers must be less than
# this value. This parameter cannot be set lower than it's
# default: 32768
max-client-read = 32768
# WebSEAL will read from a client when parsing an HTTP request.
# The total size of the URL and HTTP headers must be less than
# this value. This parameter cannot be set lower than it's
# default: 32768
max-client-read = 32768
```
When I send a request with a large header (i.e. Authorization header for SPNEGO), it is larger than max-client-read, but the authentication is successfully finished.
Why does Web Reverse Proxy accept such a large request?
Why does Web Reverse Proxy accept such a large request?
[{"Type":"MASTER","Line of Business":{"code":"LOB77","label":"Automation Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSRGTL","label":"IBM Security Verify Access"},"ARM Category":[{"code":"a8m0z000000cxuqAAA","label":"Security Verify Access-\u003EReverse Proxy"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions"}]
Log InLog in to view more of this document
This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.
Product Synonym
ISAM;ISVA
Was this topic helpful?
Document Information
Modified date:
02 September 2022
UID
ibm16617929