'Disable Caches' no longer on the Develop menu in Safari 11.0

Safari & Web General Safari Developer Tools

Tenz OP

Created Sep ’17

Replies 22

Boosts 0

Views 41k

Participants 26

There used to be a 'Disable Caches' option on the Develop menu, but it's no longer present in Safari 11.0.

It's very useful when developing not to cache the response from web servers. Is this an oversight?

It seems the only option now is to use ⇧⌘R in web inspector.

Answered by Marcok in 262612022

On Apple Release Note on Safari 11.0 there is this point:

Removed the Disable Caches menu item in the Develop menu. The equivalent functionality is now available through Web Inspector’s Network tab.

Then, option was only moved to another section 😉

Boost

shaneparsons OP

Oct ’19

I don't know if this worked back in the day, when this was posted, but it certainly doesn't work in Safari 13.0.1.

😠

spadilha OP

Apr ’20

I checked cache button on network tab (now it's red/orange) and it still not working for some files. Like the CSS in the print below. You can see it's still comming from memory cache.

https://prnt.sc/s7m9hi

fbasar OP

May ’20

Disable cache from within dev tools does not work if a reasource is selected! I dont understand this action. I use chome this property 🙂. PLEASE bring it back as before!

Hacker222 OP

Dec ’20

In the comment section on technipage.com it states

Markus says

November 23, 2020 at 3:40 am

For anyone looking into turning cache off this at a later point
of time:

Open
developer tools, go to “Network” tab, and click the small Block icon with a
line through which says “Ignore the resource cache when loading resources” in
the top right corner next to the trash icon.

It worked out for me. For anyone is looking to turn off the cache. Hope it helps.

MattyZem OP

Mar ’22

Apple, you seriously suck. Not only Safari does not follow RFC in some cases. Now you even slow down the "This fix is only for Safari" part of the dev process. OMG

gregwilker OP

Oct ’22

I take 5 years off from web dev to come back to this horse shit of an idea. Who is the developer that thought this was a good idea. **** you.

EKJ315 OP

Jun ’24

This is a long-standing bug in Safari documented by many web developers, such as at https://github.com/ElMassimo/vite_ruby/issues/258

I would assume, given how many years people have been reporting this, that it will never be fixed and Safari will never be a reliably working browser.