Skip to main content
Version: 8.2511.x.x RR

Appendix H - Deprecation List

This page lists every currently deprecated functionality of nevisProxy, with also a planned removal date. Check regularly if your current configuration is concerned about these planned removals. If one of the below feature is still used in your setup, then there is also a deprecation notice in the navajo log file, either during startup or during incoming request. If you are affected, adapt your configuration by using a replacement or contact support if you depend on the deprecated functionality.

The undocumented parameter LegacyRegexpMatching in the RewriteFilter and EncryptionFilter​

Replacement: none
Deprecated since: 9.2611.0
Plan to remove: version 10.x

The RequestURI parameter of the RewriteFilter​

Replacement: Use the parameter RequestPath instead
Deprecated since: 9.2605.0
Plan to remove: version 10.x

Description​

A whitespace or newline-separated list of rewrite rules that can be made conditional. Conditions can be added according to individual rules. Thus, the request URI can be rewritten according to values from other parts of the request header.

The MaxURISize parameter of the InputValidationFilter​

Replacement: Use the parameter MaxPathSize instead
Deprecated since: 9.2605.0
Plan to remove: version 10.x

Description​

The max. size of a request body. If not configured, an unlimited length is allowed.

The URISkippList parameter of the InputValidationFilter​

Replacement: Use the parameter PathSkipList instead
Deprecated since: 9.2605.0
Plan to remove: version 10.x

Description​

If the URI (only the path portion) matches one of the regexps, the request is passed through without any check.

The URIWhiteList parameter of the InputValidationFilter​

Replacement: Use the parameter PathWhiteList instead
Deprecated since: 9.2605.0
Plan to remove: version 10.x

Description​

Defines the rules that the URI (only the path portion) has to fulfill for the request to be passed.

The URIBlackList parameter of the InputValidationFilter​

Replacement: Use the parameter PathBlackList instead
Deprecated since: 9.2605.0
Plan to remove: version 10.x

Description​

If an URI (only the path portion) blacklist is configured, validation is successful only if the URI does not match any of the entries in the blacklist. If an URI is found in both the blacklist and the whitelist, validation also fails.

The getRequestUri function of the RequestStatistics lua class​

Replacement: Use the function getRequestPath instead
Deprecated since: 9.2605.0
Plan to remove: version 10.x

Description​

Returns the parsed request URI as well as the unparsed request URI if it differs from the parsed one.- The parsed request URI is the "translated" request URI. This URI is used to find out which filters and servlets are mapped to it.- The unparsed request URI is the URI as received from the frontend (for example the encrypted URI if an UrlEncryptionFilter was involved).