You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The wildcard matching documentation is awesome, however I think one basic example is missing or two sentences could be more useful for the customers: The "Redirect Rules" CloudFlare page mentions that By using the asterisk (*) character to create a pattern that can match many requests e.g. https://*.example.com/files/* and Please include the protocol in the Request URL. e.g. https://*.example.com, and also links the "Wildcard pattern documentation", but the docs are not clear about that we can also use the * character in the protocol part, like http*://example.com/*.
This is such a common use case that it would be really great and informative to mention this feature. A 4th example maybe or just mentioning that it is also possible, like:
The wildcard character can also be used in the protocol part, for example to create a rule that matches both http and https protocol: http*://example.com/
Additional information
No response
The text was updated successfully, but these errors were encountered:
Existing documentation URL(s)
https://developers.cloudflare.com/ruleset-engine/rules-language/operators/#wildcard-matching
What changes are you suggesting?
The wildcard matching documentation is awesome, however I think one basic example is missing or two sentences could be more useful for the customers: The "Redirect Rules" CloudFlare page mentions that
By using the asterisk (*) character to create a pattern that can match many requests e.g. https://*.example.com/files/*
andPlease include the protocol in the Request URL. e.g. https://*.example.com
, and also links the "Wildcard pattern documentation", but the docs are not clear about that we can also use the*
character in the protocol part, likehttp*://example.com/*
.This is such a common use case that it would be really great and informative to mention this feature. A 4th example maybe or just mentioning that it is also possible, like:
Additional information
No response
The text was updated successfully, but these errors were encountered: