Redirect Domain assistance, xfer, Rules?

Hello, looking to point a domain to resolve to another URL. Both on Cloudflare now, but when I set the Pages to that domain it asks to xfer it but already done. So wondering why my redirect rules are not working, help when possible. The main domain is working fine now. I just moved from replit to Cloudflare pages on missionmb.com and now want to get missionmetalbuildings.com to redirect correctly. I perfer to have https and no www, for all URLs, is that ok/perfered?
7 Replies
SuperHelpflare
SuperHelpflare2mo ago
Support AI
I'd be happy to help you with your redirect issue. To configure URL forwarding or redirects using Page Rules, you can follow these steps: 1. Go to Rules > Page Rules. 2. Under Page Rules, select Create Page Rule. 3. Under If the URL matches, enter the URL or URL pattern that should match the rule. 4. In Pick a Setting, choose Forwarding URL from the drop-down menu. 5. For Select status code, choose 301 - Permanent Redirect or 302 - Temporary Redirect. 6. Enter the destination URL. 7. Select Save and Deploy Page Rule. Please note that Page Rules require a proxied DNS record to work. Also, Page Rules will not apply to subdomains that do not exist in DNS or are not being directed to Cloudflare. Regarding your preference for HTTPS and no www, that's perfectly fine. You can configure your domain to use HTTPS and non-www by following the steps in this documentation. This will ensure that all traffic to your site is encrypted and redirected to the non-www version. If you're still experiencing issues with your redirect rules, please provide more details about your current setup and the error messages you're seeing, and I'll do my best to help you troubleshoot the issue. Source: https://developers.cloudflare.com/rules/page-rules/how-to/url-forwarding/
Feedback
Feedback has been submitted! Thank you :)
This is an AI generated response, it may not be 100% accurate. Please validate the output. You can ask followups by replying to this message or mentioning me.
Gordon Beeming
Gordon Beeming2mo ago
@Douglas Φ Technologist did the support link above help by any chance?
Douglas Φ Technologies
yes thank you, but got a bit confused this morning on some changes, and having the issues with www not redirecting.( 522 error) ... I was trying to setup R2, but going to hold off, and having trouble reverting. I have the mission-1et.pages.dev as the dest. for www & @ in the dns and for the longer domain both pointed to the short domain as redirect, all w/proxy. under Worker Mgmnt the deploy is connected to Production under Custom Domains: mission-1et.pages.dev missionmb.com , but the longer domain keep asking me to buy it, when it's already in Cloudflare, and working, just not this area. No page rule on main short domain, but on long I have missionmetalbuildings.com/* Forwarding URL (Status Code: 301 - Permanent Redirect, Url: https://missionmb.com) . . But the issue is the the sites work on root but not WWW for either. yes it did, but made a few changes and www stopped. so I'm checking again to make it work again...
Gordon Beeming
Gordon Beeming2mo ago
Not sure where that is, so didn’t know 😓
Douglas Φ Technologies
no worries, I'm going to check through the document and instructions again, and check back got it with the page rules, but I need to learn more on the difference of these levels of redirects/urlforward, etc. like when to use page rules vs rules overview, and the other styles of the settings I've seen a few places for http->https or the www to root vsvs. Looking into finding the best practices guide, and andoh hey, put in the feedback for an AI chatbot to ask questions with the updates done on CF recently.
Gordon Beeming
Gordon Beeming2mo ago
Lots of things are trial and error, I’ve done solutions work for some customers and for different setups I’ve had to change the implementation. For https, if you’re able to (make sure you have no need for gttp across the domain), switch on hsts, you can also then head to hsts preload dot org, and have it baked into browsers which at least for normal traffic will force https from the first request 🙂
Douglas Φ Technologies
got it, will do, both? and what about dnssec? and also so if Redirect from HTTP to HTTPS - All incoming requests - Automatic HTTPS Rewrites is turned on and everything working, then the site is fine to hsts? All is resolved. Seemed to do well. Thanks again for all the help.

Did you find this page helpful?