| Explanation | A configuration error has been encountered. |
| Action | Correct the configuration error. |
| Explanation | A configuration error has been encountered. |
| Action | Correct the configuration error. |
| Explanation | A configuration error has been encountered. |
| Action | Correct the configuration error. |
| Explanation | A configuration error has been encountered. |
| Action | Correct the configuration error. |
| Explanation | A configuration error has been encountered. |
| Action | Correct the configuration error. |
| Explanation | A configuration error has been encountered. |
| Action | Correct the configuration error. |
| Explanation | A configuration error has been encountered. |
| Action | Correct the configuration error. |
| Explanation | A configuration error has been encountered. |
| Action | Correct the configuration error. |
| Explanation | A configuration error has been encountered. |
| Action | Correct the configuration error. |
| Explanation | A configuration error has been encountered. |
| Action | Correct the configuration error. |
| Explanation | The number of headers on the message has exceeded the maximum limit on the number of headers |
| Action | Increase the number of headers allowed or decrease the number of headers on the message |
| Explanation | The specified value was already found by the configuration and mapped to a SameSite value. |
| Action | Ensure that cookie names and patterns are unique across the lax, none, and strict configuration lists. |
| Explanation | The wildcard (*) character was used in an unsupported way. Support consists of a single wildcard (*) character that is used as a stand-alone value, or following any number of cookie name prefixes. |
| Action | Ensure that only a single wildcard (*) character is used per pattern in the lax, none, and strict lists. Additionally, use of this character is supported only under the following two conditions: as a stand-alone value or following cookie name prefixes. |
| Explanation | The specified value was already found by the configuration and mapped to a SameSite value. |
| Action | Ensure that cookie names and patterns are unique across the lax, none, and strict configuration lists. |
| Explanation | The maximum number of decompression cycles has reached, resulting in a decompression ratio larger than the configured limit. The decompression limit is defined by the decompressionRatioLimit property. |
| Action | When this exception happens on a valid request body, reconfigure the decompressionTolerance and decompressionRatioLimit properties to achieve the appropriate decompression results. |
| Explanation | The specified value must be either a full IP address or correctly formatted hostname. |
| Action | Ensure that configured IP addresses contain a value for each segment, and that hostnames do not contain any invalid characters. |
| Explanation | The specified value must be either a full IP address or correctly formatted hostname. |
| Action | Ensure that configured IP addresses contain a value for each segment, and that hostnames do not contain any invalid characters. |