Several months ago we removed DNS entries and some page rules (301 redirects) related to using Click Funnels to sever the relationship with Click Funnels.
– Since I cannot have more than 4 “links” in my post as a new user, the following description has typos to hopefully not make my meaning less clear to get past the filter –
These page rules were something like
We added new page rules to redirect instead like this:
However, no traffic from from this redirect ever reaches
differentdomain.com if the initial request includes www. For example, domain.com goes where we want but www.domain.com continues to resolve to the old redirect and Click Funnels content. The www is currently an
A record pointing to the same IP as the bare domain’s
A record. These are the only two records on the domain. The IP is that of the registrar’s, Namecheap, and both records have orange clouds (Cloudflare CDN)
The output from
[email protected] ~> curl -I -A "Mozilla 5.0" "https://www.domain.com" HTTP/2 302 date: Tue, 25 Jan 2022 21:52:50 GMT content-type: text/html; charset=utf-8 location: https://www.domain.com/optin-17215850 cf-ray: 6d34bb16c90486fe-ORD access-control-allow-origin: * cache-control: no-cache, no-store strict-transport-security: max-age=0 vary: Accept-Encoding cf-cache-status: BYPASS access-control-allow-credentials: true access-control-allow-headers: DNT,X-CustomHeader,Keep-Alive,User-Agent,X-Requested-With,If-Modified-Since,Cache-Control,Content-Type,Authorization access-control-allow-methods: GET, PUT, POST, DELETE, PATCH, OPTIONS access-control-request-method: * expect-ct: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct" pragma: no-cache status: 302 Found x-frame-options: ALLOWALL x-powered-by: Phusion Passenger Enterprise 6.0.7 x-rack-cache: miss x-request-id: a9347f3bcd630e0ad1581e5d4690083f x-runtime: 0.217945 set-cookie: __cf_bm=4u0kEQFqdTvhl3g.ocPxWcLoJASr3kFIVKRerTWxyTE-1643147570-0-AZfv6iMOgBGGI3amPJ39eAgOgwKzJokFyKYeTuqXpFRjzL/M5RmpUVyfe1zdbYPHJPoXhtikVdWpr89XBpwY+BKCWx/gfyBTzYcRUqzTA4bk; path=/; expires=Tue, 25-Jan-22 22:22:50 GMT; domain=.www.teflproscourse.com; HttpOnly; Secure; SameSite=None server: cloudflare
We have tried:
- flushing the Cloudflare cache multiple times,
- change nameservers back to Namecheap, then re-add to Cloudflare
- delete domain from Cloudflare, change nameservers, add back to Cloudflare
- delete the new page rules and recreate them
- changed browser cache TTL to 2 minutes
- waited months for the cache to clear on its own
If we disable the Cloudflare CDN, the bad redirect goes away, but when we re-enable the CDN the bad redirect returns.
Any suggestions on what to do? Is there a big shiny red button somewhere that a Cloudflare worker could push?