I'm working with Chromium and I've encountered a frustrating caching issue. A car dealer has a link for financing that incorrectly points to a wrong domain. I set up a redirect rule to send it to the correct domain. However, I mistakenly didn't escape my capture groups, leading to the URL being improperly formed. After correcting the rewrite rule, Chromium still loads the old URL with the unescaped capture groups. I've tried clearing the cache and even checking 'Disable Cache' in DevTools, but it won't load the corrected URL. Interestingly, other browsers and online proxies redirect correctly. What could be going on?
1 Answer
Have you double-checked if it's really Chromium at fault? If you're using a CDN or have some server-side caching set up, that might be the issue. DevTools with "Disable Cache" should do the trick, but sometimes networks can have their own caching too. Maybe try on a different network? I've seen some ISPs caching aggressively.
The dealer's website is a client’s, and I don’t have direct access. I’m only managing the linked page which uses Cloudflare for DNS. I tried it on Firefox and other proxies, and it works fine.