Important: #35069 - addQueryString.exclude also applies to config.linkVars 

See forge#35069

Description 

Both addQueryString and config.linkVars carry query parameters of the current request over into generated page links. Until now addQueryString.exclude only removed a parameter from the former, so a parameter listed in config.linkVars was silently added back to the link and could not be dropped at all:

config.linkVars = print(int)

lib.link = TEXT
lib.link {
    value = A link without the print parameter
    typolink {
        parameter.data = page:uid
        addQueryString = untrusted
        addQueryString.exclude = print
    }
}
Copied!

With a request to /some-page?print=1 the generated link still contained ?print=1.

addQueryString.exclude is now honored for parameters contributed by config.linkVars as well, so the link above no longer carries the print parameter. The exclusion is only applied when addQueryString is active — config.linkVars on its own is unaffected.

Integrators who relied on config.linkVars overruling addQueryString.exclude need to remove the affected parameter from the exclude list.