Also keep in mind that doing it like this will only match the exact URL, you’ll need to include a wildcard if you want to match any URL under /post-graduate
A very easy workaround would be: implement the redirect with your .htaccess.
This saves you a PageRule, but therefore is a little bit slower, than if it would be implemented at Cloudflares Edge.
Should look something like this:
<ifModule mod_rewrite.c>
RewriteEngine on
RewriteRule "^/post-graduate(.+)" "https://pgp.kalvieducation.com/post-graduate$1" [R=301,L]
</IfModule>
or:
<ifModule mod_rewrite.c>
RewriteEngine on
RewriteRule "^/post-graduate" "https://pgp.kalvieducation.com/post-graduate" [R=301,L]
</IfModule>
or:
<ifModule mod_rewrite.c>
RewriteEngine on
RewriteRule "^/post-graduate/" "https://pgp.kalvieducation.com/post-graduate/" [R=301,L]
</IfModule>
first try with code 302 and if everything works, then switch to 301.
We’re using an upstream service for our site - so no access to editing such rules. (host is elementor).
The host is also using Cloudflare. So this won’t work- o2o.
So, this resolves it - page rules won’t work for us. I’ll have to setup something on our hosting service side.
Cloudflare team: Could’ve saved me a lot of hair pulling if CF had recognizes O2O, and provided me an error on the page rules side. It has all the information (our DNS, the A record, it’s own IP range) to present this error.