Why won't Chrome 'forget' .htaccess redirects that have since been removed from the file?

Even as a non-programmer - with your help - I've been able to use my .htaccess file various different ways... sometimes to shorten the path of long urls, sometimes to redirect to the secure version of the site... always works great.

Until I change my mind about something and remove it from the .htaccess file, because Chrome keeps acting like it's still in there. Forcing a reload of everything on the page doesn't seem to help.

Even if I hollow my .htaccess file out for the purposes of troubleshooting, it seems Chrome remembers every RewriteCond forever. (I tested it a month later and it was still redirecting, so it never expires).

Is there a way for me to flush everything Chrome knows about a specific website? In other words, treat it like it's the first time it's being pulled up, without affecting the notes it has on the other sites.

PS: Is Chrome particularly stubborn about this, or are all browsers? I know Firefox and Edge don't redirect after I removed those lines, but I had never tested the redirects on them in the first place. There was nothing for them to 'forget'. Now I'm afraid to turn the redirects back on and use those browsers, because they might have the same issue Chrome does after I turn them off (ie, keep redirecting forever) then I'm really screwed.