Chrome caching issues for web designer

[Sean]

This problem has been growing worse in worse with each version of Chrome.  It's to the point now where I'm about to ditch it entirely.

DNS Caching.  I'll use my local windows host file to change IP addresses when migrating sites to new hosts.  The change is instant in windows but Chrome caches DNS and does not bother rechecking... so I'm stuck until I restart chrome.  And yes I do know how to clear the DNS cache but it doesn't seem to work... or at least not instantly.  There is a lot of waiting/ restarting.  

The same problem happens with CSS/HTML files.  I'll make changes to CSS and chrome, even when I press F5 doesn't bother to get the latest file.  It pulls from the cache meaning I have to delete it and reload, which is time-consuming.  And yes I realize there are many components that could create HTTP cache headers.... but that is not the case here.  Literally, Chrome is starting to suck BIG LEAGUE...  I can open up Firefox or even Edge and I refresh and my changes are shown.

My last complaint is not being able to bypass HTST SSL issues.  Like I get it, but again if I'm developing something or migrating... This issue holds me up and is a pain in my butt.  There has to be a developer mode for chrome that ditches all the apples-esque tweaks that have been made that take control and functionality away and replace it for dumbed down mass consumer use.

Please make Chrome great again...

[PhistucK]

The DNS caching sounds like a bug, you should probably report it.

The reload issue, if you do use the correct HTTP header to avoid caching, sounds like a bug as well.

(Note that there have been changes to the reload functionality recently that probably made this worse if you do not have cache-avoiding HTTP headers - https://blog.chromium.org/2017/01/reload-reloaded-faster-and-leaner-page_26.html)

Though I advise you to use Control + F5 and not only F5. That has been the best practice for decades (alternatively, tick the "Disable cache" check box in the Network panel of the Developer Tools and everything will be loaded from the server no matter what you press, as long as the Developer Tools feature is open).

For any bug you find (one bug per report) -

You can search crbug.com for an existing issue and star it. If you cannot find one, file a new issue using the "New issue" link on the same page.

Please, do not add a "+1" or "Me too" or "Confirmed" (or similar) comment. It just wastes the time of Chrome engineers and sends unnecessary e-mails to all of the people who starred the issue.

You can reply with a link to the found or created issue and might get triaged (and fixed) faster.

Thank you.

☆PhistucK

--
--
Chromium Discussion mailing list: chromium...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-discuss

---
You received this message because you are subscribed to the Google Groups "Chromium-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-discuss+unsubscribe@chromium.org.