Custom filter expression redirect rules are all being changed to wildcard redirect

What is the name of the domain?

aevenia.com

What is the issue you’re encountering

New & previously working ‘Custom filter expression’ rules are being changed to wildcard redirect rules.

What steps have you taken to resolve the issue?

We have deleted rules and tried to re-create them. Each time the selection is changed from ‘Custom filter expression’ to ‘wildcard’.

What are the steps to reproduce the issue?

Go to website, select rules → redirect rules → create custom expression → save.

Refresh and go back into the rule and it now shows as a wildcard.

Does it create any issues for you? This should only happen if your custom expression can actually still be parsed as a simple wildcard rule.

If you have logical conditions like OR, or if you are using operators like equals, contains and so on or functions like regex_replace(), you should still see the custom filter expression view normally.

Yes. The non-standard http ports don’t redirect (8082, etc.) properly with the wildcard rule. I ended up creating a second condition (or) and it no longer replaces the custom filter and includes the non-standard http ports.

This can be closed as resolved.

This topic was automatically closed after 15 days. New replies are no longer allowed.