VALD
The next table lists all error codes related to the validation filters.
| Major | Minor | Message | Details |
|---|---|---|---|
| VALD | 0001 | parsing failed. | The parsing of an XML body failed. Check the log file for further information. |
| 0002 | blocking xml because of the following schema-location. | A request is blocked due to an invalid schema location. Check the log file for further information. | |
| 0003 | no processing rule found. | The XMLFilter blocks a request for which no rule has been configured. Check the log file for further information. | |
| 0004 | xml body denied. | The XMLFilter blocks a request due to a given rule. Check the log file for further information. | |
| 0005 | xml body denied, logging only. | The XMLFilter would block a request due to a given rule, if the filter parameter BlockOnError would be on. Check the log file for further information. | |
| 0006 | could not read a schema entity. | A schema entity could not be read. This is most probably due to a permission problem. Check your configuration (in the web.xml file). Check the log file for further information. | |
| 0007 | could not resolve a schema entity. | A schema entity could not be resolved. Check your configuration (in the web.xml file). Check the log file for further information. | |
| 0008 | schema entity failed. | A schema entity could not be loaded. Check the log file for further information. | |
| 0009 | schema entity failed unknown exception. | Contact support. | |
| 0010 | Drop-rules are not allowed as 'ParameterRules'. | The ParameterValidationFilter does not support drop rules. Check your configuration (in the web.xml file). | |
| 0011 | unknown action,. Only 'allow, 'required', 'drop', and 'deny' are allowed | A validation rule contains an invalid action. Check your configuration (in the web.xml file). | |
| 0012 | unknown logmode. Only 'log', and 'silent' are allowed | A validation rule contains an invalid action. Check your configuration (in the web.xml file). | |
| 0013 | deny request with status as defined in rule | A request is blocked as configured in the corresponding rule. | |
| 0014 | required is missing, as defined in rule | A request may be blocked due to a required value, as configured in the correspondent rule. | |
| 0015 | a black-listed rule was triggered | A request will be blocked due to a blacklisted configuration rule. | |
| 0016 | error verifying url | The EnryptionFilter could not verify a URL. The request may be blocked, depending on the configuration. | |
| 0017 | decrypting url failed | The EnryptionFilter could not decrypt a URL because the size did not match. The request may be blocked, depending on the configuration. | |
| 0018 | decrypting url failed | The EnryptionFilter could not decrypt a URL. Check the log file for more information. The request may be blocked, depending on the configuration. | |
| 0019 | soap/xml body denied, log only mode. | The Soap**Filter would block a request due to a given rule, if the filter parameter BlockOnError would be on. Check the log file for further information. | |
| 0020 | soap/xml body denied. | The SoapFilter blocks a request due to a given rule. Check the log file for further information. | |
| 0021 | Invalid line: syntax must be <name_regex>:<value_regex>. (Have you forgotten to escape the colon?). | Check your configuration (in the file web.xml). | |
| 0022 | JSON is not correct | The JSONFilter cannot read a JSON body. Check the log file for further information. The request may be blocked, depending on the configuration. | |
| 0023 | element is not a regular expression | Contact support. | |
| 0024 | could not read schema file | A schema file could not be loaded. This is most probably due to a permission problem. Check the log file for further information. Check also your configuration (in the file web.xml). | |
| 0025 | problem occurred while formatting the error message | Contact support. | |
| 0026 | 'items' in schema is not of JSONArray type | The JSON body has an invalid schema. The request may be blocked, depending on the configuration. | |
| 0027 | json body denied, log only mode | The JSON body is denied, but the request is not blocked due to the configuration of the corresponding filter ("log mode"). See the log file for further details. | |
| 0028 | json body denied | See the log file for further details. The request will be blocked. | |
| 0029 | cleanup of the CSRFFilter failed. | Contact support. | |
| 0030 | no InjectionScriptPath given, while InjectedIdCheck = true. | Check your configuration (in the file web.xml). | |
| 0031 | Error reading the script file. | Check your configuration (in the file web.xml). | |
| 0032 | no processing rule found. | The CSRFFilter blocks a request because no rule was found or configured for this request. | |
| 0033 | CSRFFilter check failed, request blocked. | The CSRFFilter blocks a request because the request did not match the needed conditions. Check the log file for further details. | |
| 0034 | CSRFFilter check failed, request passed through. | Although a request did not match the needed conditions, the CSRFFilter does not block it because of the filter's configuration ("log mode"). Check the log file for further details. | |
| 0035 | CSRFFilter check failed, request redirected. | The CSRFFilter redirects a request that did not match the needed conditions. Check the log file for further details. | |
| 0036 | Invalid CSRFPolicy, request dropped. | Contact support. | |
| 0037 | cleanup of the EncryptionFilter failed. | Contact support. | |
| 0038 | replacing uri for redirection failed. | Contact support. | |
| 0039 | request blocked. | The EncryptionFilter blocked a request, because the request did not match the conditions. Check the log file for further details. | |
| 0040 | request passthrough. | Although a request did not match the conditions, the EncryptionFilter does not block it because of the filter's configuration ("log mode"). Check the log file for further details. | |
| 0041 | verifyParameters failed. | The EncryptionFilter blocks a request due to an error. Contact support. | |
| 0042 | verifyParts failed. | The EncryptionFilter blocks a request due to an error. Contact support. | |
| 0043 | parameters blocked. | The EncryptionFilter blocked a request because a parameter did not match the conditions. Check the log file for further details. | |
| 0044 | parameters passthrough. | Although a parameter did not match the conditions, the EncryptionFilter does not block the request because of the filter's configuration ("log mode"). Check the log file for further details. | |
| 0045 | no css-rules 'ContentTypes.css' found. Check your configuration. | Check your configuration (in the file web.xml). | |
| 0046 | no javascript-rules 'ContentTypes.javascript' found. Check your configuration. | Check your configuration (in the file web.xml). | |
| 0047 | Content-Type='text/[html]' with Content-Encoding not supported, subsequent requests will fail. | The backend sent a response with a content encoding header. This is not supported by the EncryptionFilter. To solve this problem, map a InflateFilter between the EncryptionFilter and the backend. | |
| 0048 | Invalid syntax. Expected: <type>:<name-regex>. | The EncryptionFilter has a syntax error in the parameter ExtraFormRules. Check your configuration (in the file web.xml). | |
| 0049 | multipart request is empty. | The EncryptionFilter blocked a request due to an empty multi-part request. | |
| 0050 | multipart form signature part verification failed. | The EncryptionFilter blocked a request because the signature in the multi-part could not be verified. | |
| 0051 | Form descriptor verification failed. | The EncryptionFilter blocked a request because the signature of the form descriptor in the multi-part could not be verified. Check the log file for further details. | |
| 0052 | form open already called. | The EncryptionFilter may block a request because the form target sent by the backend is malformed. Check the log file for further details. Also check your backend. | |
| 0053 | illegal form open not called. | The EncryptionFilter may block a request because the input target in a form sent by the backend is malformed. Check the log file for further details. Also check your backend. | |
| 0054 | illegal form open not called. | The EncryptionFilter may block a request because the test area target in a form sent by the backend is malformed. Check the log file for further details. Also check your backend. | |
| 0055 | missing name. | The EncryptionFilter may block a request because the test area target in a form sent by the backend does not have a name. Check the log file for further details. Also check your backend. | |
| 0056 | illegal form open not called. | The EncryptionFilter may block a request because the select target in a form sent by the backend is malformed. Check the log file for further details. Also check your backend. | |
| 0057 | missing name. | The EncryptionFilter may block a request because the select target in a form sent by the backend does not have a name. Check the log file for further details. Also check your backend. | |
| 0058 | illegal form open not called. | The EncryptionFilter may block a request because the option target in a form sent by the backend is malformed. Check the log file for further details. Also check your backend. | |
| 0059 | missing value inside closing tag. | The EncryptionFilter may block a request because the option target in a form sent by the backend does not have a value. Check the log file for further details. Also check your backend. | |
| 0060 | illegal no previous select field. | The EncryptionFilter may block a request because the select target in a option sent by the backend is malformed. Check the log file for further details. Also check your backend. | |
| 0061 | form open not called. | The EncryptionFilter may block a request because the form target sent by the backend is malformed. Check the log file for further details. Also check your backend. | |
| 0062 | illegal serialID. | The EncryptionFilter may block a request because the ID was invalid. Check the log file for further details. | |
| 0063 | error verifying signature. | The EncryptionFilter may block a request because the signature could not be verified. Check the log file for further details. | |
| 0064 | error verifying signature. | The EncryptionFilter may block a request because the signature could not be verified due to an error. Check the log file for further details. | |
| 0065 | field not verified. | The EncryptionFilter may block a request because an input field could not be verified. Check the log file for further details. | |
| 0066 | a response header is denied. | A response header will not be sent back to the frontend, as configured in the corresponding filter. Check the log for further details. | |
| 0067 | blocking request. | A request will be blocked, as configured in a rule in the corresponding filter. Check the log for further details. | |
| 0068 | Rewriting HTML with Content-Encoding not supported, no Javascript will be injected. | The CSRFFilter does not support the Content-Encoding header; no Javascript will be injected in the response. Map an InflateFilter between the backend and the CSRFFilter to fix this problem. | |
| 0069 | cleanup of the InputValidationFilter failed. | Contact support. | |
| 0070 | You have to set a 'AuditLog.Key' for the 'AuditLog.FileName'. | Check your configuration (in the file web.xml). | |
| 0071 | deny header. | The InputValidationFilter blocks a request due to an invalid header, as configured in a rule. Check the log for further details. | |
| 0072 | blocking request with missing header. | The InputValidationFilter blocks a request due to a missing header, as configured in a rule. Check the log for further details. | |
| 0073 | deny parameter. | The InputValidationFilter may block a request due to an invalid header, as configured in a rule. Whether the request is really blocked depends on the configuration of the filter parameter BlockOnError. Check the log file for further details. | |
| 0074 | HTTP headers found. | The InputValidationFilter found more request headers than is allowed according to the filter parameter MaxHeadersAllowed. The request may be blocked, depending on the configuration. Check the log for further details. | |
| 0075 | request body too long size. | The request body is bigger than configured in the parameter MaxBodySize of the InputValidationFilter. The filter may block the request, depending on the setting of the filter parameter BlockOnError. Check the log for further details. | |
| 0076 | maximum number of parameters reached. | The request has more parameters than configured in the parameter LimitRequestParameters of the InputValidationFilter. The filter may block the request, depending on the setting of the filter parameter BlockOnError. Check the log for further details. | |
| 0077 | invalid Content-Disposition. | The request may be blocked by the InputValidationFilter due to an invalid "Content-Disposition" in a form data. Whether the filter really blocks the request depends on the configuration of the filter parameter BlockOnError. Check the log file for further details. | |
| 0078 | required parameter is missing. | The request may be blocked by the InputValidationFilter due to a missing parameter. Whether the filter really blocks the request depends on the configuration of the filter parameter BlockOnError. Check the log file for further details. | |
| 0079 | Request URI too long. | The request URI was longer than configured in the parameter MaxURISize of the InputValidationFilter. The filter may block the request, depending on the setting of the filter parameter BlockOnError. Check the log for further details. | |
| 0080 | Request query string too long. | The request query was longer than configured in the parameter MaxQuerySize of the InputValidationFilter. The filter may block the request, depending on the setting of the filter parameter BlockOnError. Check the log for further details. | |
| 0081 | a value is missing. | A value was missing in the request. The InputValidationFilter may block the request, depending on the setting of the filter parameter BlockOnError. Check the log for further details. | |
| 0082 | name/value does not match any rule. | A name/value pair did not match any whitelist rule. The InputValidationFilter may block the request, depending on the setting of the filter parameter BlockOnError. Check the log for further details. | |
| 0083 | name='%s' not in map. | A name did not match any of the parameters AllowedHeaders or AllowedMethods of the InputValidationFilter. The filter may block the request, depending on the setting of the filter parameter BlockOnError. Check the log for further details. | |
| 0084 | couldn't base64-decode raw data. | Contact support. | |
| 0085 | Failed to resolve entry. | Check the logs for more details. | |
| 0086 | Unknown execption. | Contact support. | |
| 0087 | Failed to cleanup XMLValidaitonFilter. | Check the logs for more details. | |
| 0088 | No targetNamespace or valid schema found in wsdl-file | Check your configuration. | |
| 0089 | Could not parse wsdl-file. | Check your configuration. | |
| 0090 | No schemas found in wsdl-file. | Check your configuration. | |
| 0091 | No messages found in wsdl-file. | Check your configuration. | |
| 0092 | Parsing failed with OutOfMemoryException | Contact support. | |
| 0093 | Parsing failed with XMLException. | Check the logs for more details. | |
| 0094 | Body size overlimits the configured max size. | Increase the configured size. | |
| 0095 | Message not found or invalid. | Check the logs for more details. | |
| 0096 | Checking the SOAP namespace failed. | The name space was not found or invalid. | |
| 0097 | Parsing failed with IOException. | Check the logs for more details. | |
| 0098 | Parsing failed with OutOfMemoryException. | Check the logs for more details. | |
| 0099 | Parsing failed with XMLException. | Check the logs for more details. | |
| 0100 | Parsing failed with Throwable | Check the logs for more details. | |
| 0101 | Parsing failed with unknown exception. | Contact support. | |
| 0102 | Illegal redirect-url (Location header is invalid). | Check the logs for more details. | |
| 0103 | Too many redirects. | Contact support. | |
| 0104 | Failed to download scema. | Check logs for more details. | |
| 0105 | Resolving schema failed. | Check logs for more details. | |
| 0106 | Exception during storing the entity. | Check logs for more details. | |
| 0107 | Servlet not found. | Check your configuration. | |
| 0108 | Download the entity failed with IOException. | Check logs for more details. | |
| 0109 | Download the entity failed with ServletException. | Check logs for more details. | |
| 0110 | Download the entity failed with Throwable. | Check logs for more details. | |
| 0111 | Parsing failed. | Contact support. |