Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The wildcard matching documentation should mention the http*:// example/possibility #17945

Open
Peneheals opened this issue Nov 2, 2024 · 0 comments · May be fixed by #18181
Open

The wildcard matching documentation should mention the http*:// example/possibility #17945

Peneheals opened this issue Nov 2, 2024 · 0 comments · May be fixed by #18181
Assignees
Labels
content:edit Request for content edits documentation Documentation edits product:ruleset-engine

Comments

@Peneheals
Copy link

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/* 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

@Peneheals Peneheals added content:edit Request for content edits documentation Documentation edits labels Nov 2, 2024
@pedrosousa pedrosousa linked a pull request Nov 15, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
content:edit Request for content edits documentation Documentation edits product:ruleset-engine
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants