Page rule depth

We recognized that a page rule with 3 slugs (or asterix) works but with 4 slugs not (even without asterix). Is this true? Is there a documentation?

You can use up to five wildcards and these get properly mapped to their respective variables.

$ curl -I http://DOMAIN/hello/world/foo/bar/test
HTTP/1.1 302 Moved Temporarily
Location: http://example.com/hello/world/foo/bar/test

Setting mirage to off works with: example.com/g/* but not with example.com/g/foo/assets/* . Even disabling with the full url copied from the browser this doesn’t work for example.com/g/foo/assets/clouds.png. Why?

Post a screenshot of your page rule and a sample URL.

Also, Mirage needs to be applied on the document URLs, not image URLs.

image

Using the rule vrdoro.com/g/* disables mirage (for the whole page) but we understand the documentation that it is possible to define a rule for a resource like https://vrdoro.com/g/nbank/assets/clouds.png. Or can we only disable mirage for the whole page? I think we need to avoid the attribute data-cfsrc for the images. With this tag our aframe.io applicaton doesn’t work. I think the problem is in our case, that the mirage script is loaded in the asset section which preloads the images.

As I wrote, you need to apply it to the document, not the images.

Thanks, I got it. So I think: That should be mentioned when a rule is used to disable mirage (it may the case for other actions on rules). The documenation can be much better. For now even the Learn more link at the mirage section (https://support.cloudflare.com/hc/de/articles/218411427) is broken.

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.