Can I redirect all traffic to https://www.* with a single page rule?

[Flanders]

I don’t want to use Always Use HTTPS because it gets in the way of Cloudflare workers.

This page rule doesn’t work:

*example.com/*
Redirect
https://www.example.com/$2

It says it would cause an infinite redirect loop even though it wouldn’t actually because I have a higher priority page rule on https://www.example.com/*

[fritexvz]

May I ask if you have got both A www and A yourdomain.com (or CNAME?) records at your DNS dashboard?

What SSL option have you got selected under SSL tab/settings page for your domain?

Maybe this could help?:

Using page rules to perform redirects

Introduction to redirecting with page rules video [Cloudflare Community Tutorial - Redirecting with Page Rules in Cloudflare] Specific Use Cases You may find a specific tutorial for your use case here, if not then below is some general information and guidance: Redirect example.com to www.example.com Redirect www.example.com to example.com Redirecting One Domain to Another Forward A Subdomain To Discord DNS Records for Page Rules From the Cloudflare Help Center: R…

Redirect example.com to www.example.com

This tutorial covers redirecting example.com to www.example.com when using Cloudflare, to do the opposite, please see Redirect www.example.com to example.com. You should replace all instances of example.com in the screenshots with your domain. Step 1, The DNS Record: The first thing you will need is a DNS record for @, set to . This can point to any IP address as the redirection page rule will execute first. I would recommend pointing it to 192.0.2.1, a dummy IP. [image] Step 2, Th…

Using Wildcards in Page Rules

The basic page rule If we have a page rule set to match: example.com It will match both http://example.com and https://example.com. You do not need to specify http:// or https:// to match in the page rule, unless you want to limit it to only trigger on that protocol. You do not need a wildcard (*) to match both http and https. Wildcards In page rules, the asterisk (*) can be used as a wildcard, for instance, if we have a page rule set to match: example.com/a*z It will match example.com/abc…

Troubleshooting redirect loop errors

Configuring URL forwarding or redirects with Cloudflare Page Rules

[Flanders]

I have both HSTS and Always Use HTTPS disabled.

[Flanders]

I guess I should clarify my question. Can I redirect all traffic to https://www.* with a single page rule? I only know how to do it with two page rules which seems like a waste of a page rule. This page rule doesn’t work:

*example.com/*
Forwarding URL
https://www.example.com/$2

It says Forwarding URL matches the target and would cause a redirect loop. However it would not really cause a redirect loop because I have a higher priority page rule on https://www.example.com/*

[MattElekHarris]

I also have this problem. In fact, I actually used to have this exact page rule, but I think the validation must have updated because I cannot add it back. This is especially useful for redirecting multiple subdomains (m, ww1, etc) as well, which also can’t be done.

[Flanders]

This doesn’t help me because I’m trying to do this with a page rule. But it might help you. Instead of a page rule you could use a Cloudflare worker:

addEventListener("fetch", event => {
	const request = event.request;
	const origin = "https://www.example.com/";// redirect all requests to this host
	if (request.url.slice(0, origin.length).toLowerCase()==origin) {// fetch requested URL
		event.respondWith(fetch(request));
	}
	else {// redirect request to new origin
		event.respondWith(new Response("", {status: 301, headers: {location: origin+request.url.split(/^https?:\/\/[^\/]+\//i)[1]}}));
	}
});

Then you have to add it to a Route on *example.com/*

[MattElekHarris]

Thanks! I already do something like that, but I would like to use workers to accomplish this too.