Safari CSS caching bug

I now have two clients that prefer to use Safari.
The problem is that is appears that Safari has a really nasty
habit of
caching CSS files and not refreshing them. Anyone know of a
workaround for
that in Safari's settings or anything?
-Darrel
=================================================================
Win prizes searching google:
http://www.blingo.com/friends?ref=hM72-GU3FWzMFnTqhv-2GE1FNtA

Safari > Empty Cache...
James M. Shook
http://www.jshook.com

Similar Messages

  • Safari redirect caching bug

    At some point recently, Safari's caching with respect to 302 redirects changed.
    I have the following setup:
    URL A is handled dynamically, and redirects the user to one of several possibilities.
    One of the possibilities is to redirect (302) to a static HTML page.
    If I start up a fresh Safari process then the first time I go to URL A, then it's handled correctly. Any subsequent attempts to go to URL A result in the browser immediately showing the cached static content, and never hitting A.
    This still works as expected (ie how it's been working for the last few years) on all other browsers, but it looks like this behaviour changed with the most recent Safari releases. It's true for Safari 7.0 on Mavericks and 6.1 (8537.71) on Mountain Lion.
    Obviously I can code round this, but the behaviour seems surprising.
    Neil

    I'm seeing this behavior on iOS 7 Safari, probably older versions as well though I've not confirmed yet.
    We have a web filter. When a web page is blocked, a 302 redirect is issued redirecting to a block page which tells the user that the site is blocked, why it is blocked, and lets them log in to bypass the block. Upon logging in, the user should not longer be redirected to a block page. Revisiting the blocked site, now unblocked, results in the 302 redirect again. The only solution is to clear safari cache and try again, but this is too complicated for the majority of users.

  • Safari takes minutes to become responsive after launch (favicon/cache bug?)

    This problem is driving my crazy. Seem to have had it forever across all my macs and just can't believe I'm alone.
    If I restart my mac and launch Safari, it will launch in a few bounces BUT it remains un-usable for literally minutes. The homepage half loads then beach ball time, not of the interface buttons respond. This goes on for 5+ minutes. When it does let me interact it's slow but after a few minutes more it will go back to normal. If I look in my bookmarks menu I notice all the favicons have reverted to the general bookmark icon.
    This happens every single time I restart my mac without fail. I'm forever force quitting, waiting and twiddling my thumbs for it to wake up.
    Surely I can't be alone. This problem is much more noticable on my CD macbook than it is on my C2D iMac. The issue was the same with safari 3 as it is with v4.

    The following usually works on both Tiger and Leopard:
    (First, if yours is an Intel Mac, check that Safari is not running in Rosetta, which is enough to slow it to a crawl.)
    Adding DNS codes to your Network Settings, should gives good results in terms of speed-up:
    Open System Preferences/Network. Double click on your connection type, or select it in the drop-down menu. Click on TCP/IP and in the box marked 'DNS Servers' enter the following two numbers:
    208.67.222.222
    208.67.220.220
    (An explanation of why that is both safe and a good idea can be read here: http://www.labnol.org/internet/tools/opendsn-what-is-opendns-why-required-2/2587 / )
    Whilst in System Preferences/Network you should also turn off 'IPv6' in your preference pane, as otherwise you may not get the full speed benefit (the DNS resolver will default to making SRV queries). If you want to know what IPv6 is:
    This is Apple's guidance on iPv6:
    http://docs.info.apple.com/article.html?path=Mac/10.5/en/8708.html
    Click on Apply Now and close the window.
    Restart Safari, and repair permissions.
    If that didn't do it, then try this as well:
    Empty Safari's cache (from the Safari menu), then close Safari.
    Go to Home/Library/Safari and delete the following files:
    form values
    download.plist
    Then go to Home/Library/Preferences and delete
    com.apple.Safari.plist
    Repair permissions (in Disk Utility).
    Start up Safari again, and things should have improved.
    Less likely, but possible, is that the slowness is caused by a Trojan such as the one called 'DNSChanger' or 'OSZ.RSPlug', which can alter the DNS settings of your network connection. This particular Trojan can be inadvertently installed if you have come across certain Quicktime movies where got a window stating that you have to download and install a particular codec in order to see the video.
    If you have agreed to that installation, your system can be infected and your DNS settings altered, which results in your system using the wrong DNS servers, which can slow web surfing to a crawl.
    This can be fixed by downloading and running a freeware utility called DNSChanger Removal Tool which you can download from here:
    http://www.versiontracker.com/dyn/moreinfo/macosx/33696
    Once you have run that utility you have to re-boot your Mac, then reset Safari, and re-enter your DNS settings in System Preferences/Network.

  • Safari incorrectly caches window.setTimeout in setTimeout loop

    I submitted an Apple bug report for this issue, but I wanted to post it to a public forum in case others have experienced this issue. It appears that Safari incorrectly caches the value of window.setTimeout (and does not respect new values to which it is set) if it exceeds a certain number of executions in a setTimeout loop. It's probably best shown through an example.
    To reproduce, create an HTML page with the following content, and open it in Safari with the JavaScript console open:
    <!DOCTYPE html>
    <script>
    var MAX_RETRY = 99;
    var count = 0;
    function retry() {
      console.log('retry called');
      if (count++ < MAX_RETRY) {
        window.setTimeout(retry, 10);
      } else if (next) {
        next();
    var next = function() {
      next = null;
      window.setTimeout = function() {
        console.log('fake set timeout called');
      count = 0;
      console.log('second retry attempts');
      retry();
    console.log('first retry attempts');
    retry();
    </script>
    All browsers except Safari correctly output the following to the JS log:
    first retry attempts
    retry called (100 times)
    second retry attempts
    retry called
    fake set timeout called
    Safari does not respect the reassignment of window.setTimeout after it has executed in the setTimeout loop too many times. It instead outputs the following:
    first retry attempts
    retry called (100 times)
    second retry attempts
    retry called (100 times)
    If you decrease the value of MAX_RETRY enough, Safari will eventually respect the new value of window.setTimeout. On Safari 6.0.5, MAX_RETRY seemingly has to be <= 8. On earlier versions of Safari, it has to be even lower.

    Thanks for the info! Very useful to not become crazy while debugging it

  • Safari and cache?

    safari 4.04
    for an extended time I have had the recurring issue of safari becoming slower and slower... if I am at a site for example espn.. and engaged on a forum... I will encounter problems with posting messages... such as not being able to contact the site... safari just seems to progressively become more twitchy and sluggish over a period of use... my question?
    in an attempt to find some level of improving this situation... tried clearing the cache using the safari menu... after this not seeming to have an effect... went to my user library and looked at safari's cache size.. which was around 700-800 mb... what was interesting is after using the safari menu to clear the cache... the size of the cache folder changed very little... so I tried a more extreme approach and just tossed the entire safari cache folder in the trash and deleted... restarted safari and it appeared to be much more responsive... but what I also observed is that within a very short period.. couple of hours... bang up to 600-700 mb of cache...

    In the great scheme of things, that is not a very large cache. If your Safari seems slow:
    (First, if yours is an Intel Mac, check that Safari is not running in Rosetta, which is enough to slow it to a crawl. If you are running Snow Leopard, run Safari in 32 bit not 64 bit.)
    Adding DNS codes to your Network Settings, should gives good results in terms of speed-up as well as added security:
    Open System Preferences/Network. Double click on your connection type, or select it in the drop-down menu, and in the box marked 'DNS Servers' add the following two numbers:
    208.67.222.222
    208.67.220.220
    (You can also enter them if you click on Advanced and then DNS)
    (An explanation of why that is both safe and a good idea can be read here: http://www.labnol.org/internet/tools/opendsn-what-is-opendns-why-required-2/2587 /
    Open DNS also provides an anti-phishing feature: http://www.opendns.com/solutions/homenetwork/anti-phishing/ )
    Wikipedia also has an interesting article about Open DNS:
    http://en.wikipedia.org/wiki/OpenDNS
    Whilst in System Preferences/Network you should also turn off 'IPv6' in your preference pane, as otherwise you may not get the full speed benefit (the DNS resolver will default to making SRV queries). If you want to know what IPv6 is:
    This is Apple's guidance on iPv6:
    http://docs.info.apple.com/article.html?path=Mac/10.5/en/8708.html
    Click on Apply Now and close the window.
    Restart Safari, and repair permissions.
    If that didn't do it, then try this as well:
    Empty Safari's cache (from the Safari menu), then close Safari.
    Go to Home/Library/Safari and delete the following files:
    form values
    download.plist
    Then go to Home/Library/Preferences and delete
    com.apple.Safari.plist
    Repair permissions (in Disk Utility).
    Start up Safari again, and things should have improved.
    More useful information here:
    http://guides.macrumors.com/SpeedupSafari

  • Can't believe the caching bug is STILL there

    Hi,
    I MUST be missing something. It can't be true that this has not been fixed after so many years.
    So well, the problem is, every time you load an external asset or file, say for example using a Loader object or a URLLoader object (the same happened in AS2 with MovieClipLoader, LoadVars, XML.load() etc etc, and even before with loadMovie, etc) - every time you load a file, the Flash Player caches that file, and this is independent from your browser: it is Flash Player's own (and primitive) caching mechanism.
    Whenever you load a file with the same URL again, no matter whether the file has been changed or not, Flash Player will use the cached copy, and there's NO WAY to prevent that - there are a few workaround that I will discuss later but they don't solve the problem completely, besides being terribly combersome.
    Now, the HTTP protocol has a wonderful mechanism to manage the caching of files in an intelligent way, which has been working for years and, I think, was invented even before flash existed, however at least 10 years ago, and it works fine.
    If an HTML page has an IMG tag with an image, for example, and if the browser has already a cached version of the image with that URL, the browser will first ask the server for that file and declare it has a cached version with date xxx; if the server's file is not newer than xxx, then the server replies that the file has not changed and the browser can use its cached version (or insist to redownload it if he wishes). But if the file on the server is newer, the server will reply with the new file, and the browser will NEVER show an obsolete cached version of the image (or whatever file).
    Now, I don't know why, Flash Player was designed in a very primitive way that ignores this whole mechanism provided and standardised by the HTTP protocol. Flash Player will ALWAYS use a cached version of the file if he has one, it won't worry about veryfying whether it is obsolete or not.
    So, unless the user clears its cache, whenever you update an xml, txt, jpg or whatever file that is loaded within your flash application, users that have previously visited the page may still see the old version.
    Now, there's an easy workaround for ensuring that a cached version of the file is NEVER used, which is appending a "?somerandomname="+n to the filename, where n is obtained for example as n=(new Date()).value(); in order to ensure that it is always different.
    This way, the complete url of the file is always different and the cached version will never be used.
    However, this is not a solution either. For small text files it is ok, but for images and swf's for example, you DO want the cached file to be used IF it is not obsolete. Otherwise, returning visitors will always have to wait for the complete download time of everything, including files that have been downloaded yesterday and have not been modified.
    So, this problem has been solved ages ago by the HTTP protocol, but the Flash Player is naive and ignores it.
    I used to use 2 workarounds: the one I have mentioned for small files (texts, xml's), and the following one for files that can be updated every once in a while:
    In the main html page, I append "?lastupdate=dddddd" to the swf name, where dddddd is a manually edited date of the last time something relevant has been updated. So for example:
    <object ....... etc etc> <param name="movie" value="mainswffile.swf?lastupdate=20090625"/>... <embed etc etc etc src="mainswffile.swf?lastupdate=20090625"/></object>
    Or something like that.
    When I update some of the files that are to be loaded, I manually edit the "lastupdate" thing in the html.
    Then in the ActionScript programming I use the _root.lastupdate variable to append to the filenames of images or assets I load.
    All this is horribly cumbersome and error-prone. Image you deploy a website to a client that will be able to update his own texts and images: you have either to explain him how to edit the html file also, or create some complicated server-side or client-side script to manage the cache-avoiding system. That is, reinventing the wheel, in this case the cache.
    Every time a new version of the player was released, I expected it to fix the stupid caching problem and to make my cumbersome tricks obsolete and unnecessary.
    I expected to see that the new version would make proper use of HTTP caching protocol specifications, and use cached files ONLY when they are not outdated, after verifying it with the server according to the HTTP protocol.
    Every new version of the player was a disappointment.
    Then I hope the new version of the language, Action Script 3.0, would fix this.
    No, it seems it doesn't.
    I've done some tests with AS3 and with my great and sad surprise, the caching "bug" is still there.
    Well, the bug, not the "bug": this is a bug proper, because there's no reason why it should work this way.
    So, my question is.
    Maybe am I missing something? Is there a way, by using some method or property of URLLoader, Loader and/or URLRequest, to tell Flash Player to use the cache in an intelligent way? I mean, in a not-astonishingly-stupid way?
    Note that I'm not talking about forcing it to NOT USE cache at all: I mean using a cached version when it is appropriate, and redownloading the file when needed, as all decent http application have done for years.
    Perhaps there IS a way to solve this.... It should be the default behaviour and should be transparent, but however, if there is a SERIOUS fix (not a hackaround), that would at least solve the problem.
    Do anybody know of a method that really works?
    (I have read of people trying by using http headers with caching directives but without success; or in the best case maybe they were able to force never-caching, which is NOT a solution as I explained)
    Thanks in advance.
    And if there is any Adobe developer listening, please fix this bug since it is really a shame that an application written in 2008 or 2009 suffers from a problem that was elegantly and definitely solved in the XX century.
    Regards,
    m.

    I wrote a long reply and when I posted it it vanished.
    I had even control+c'opied it before submitting but it didn't even get into my clipboard.
    Shame on this forum (sorry to say that, but that's what I have to say).
    So, I'll try to write it again but it won't be the same: the amount of rage is augmented.
    Thank you BWolfe for letting me know that Flash now (since last year) has a bug management system. It was also such an enormous shame that it didn't have one.
    Adobe used to confuse bug reports with feature requests; now this kind of confusion is still partially there and it is reflected by the voting thing, which is an absolute aberration. In a decent bug management system, the developers take the responsibility to give the bugs the priority they deserve; and no matter how low the priority, even the smallest bug ALWAYS get into the queue.
    Now this bug we are discussing has been well known for AT LEAST EIGHT YEARS and I am not exaggerating at all, as I started using flash in 2001 and the issue was already mentioned here and there in forums etc; probably some blind people didn't see it as a bug (rather as a situation you have to face or work around), but it was known. And the very solution, as I already pointed out, was there even before Flash was conceived (well, for the sake of scientifical rigour, I should say, before Flash was commercialized): the HTTP protocol has the capability to perfectly manage file caching in a manner transparent to the higher layer.
    So, since I don't believe that nobody at Adobe (formerly Macromedia) has heard about a bug that every intermediate-level actionscript developer in the world knows of, it is already kind of a shame that we have to report it in 2009, but that's ok. But that we have to get votes, no, that's an insult.
    Jesus, ActionScript is a programming language, man, A PROGRAMMING LANGUAGE... it is not like Photoshop or Premiere; and it seems like in so many years, people who manage it haven't yet realised it completely.
    Big Brother contestants should be voted. Feature requests may be voted. Bugs cannot be voted should just be fixed one by one as soon as possible.
    Well, sorry for the rant and thank you for the answers.
    Hope this gets through this time.

  • Safari not caching on iPad?

    When I open a new page then come back to the previous one, rather than just displaying the previous page just as it was when I minimized it by opening a new page Safari tends to redownload the page. This wastes time and bandwidth. I don't think Safari does this in my iPhone or desktop. I don't see any settings I can change. Is this normal? Does anybody else find it as annoying as I do?
    Another small issue is that when I open a new page Safari places the insertion bar in the Google search field rather than the url field. This too is annoying and a time waster forcing me to reposition the insertion bar. Is there a way to cause Safari to place the insertion bar in the URL field by default.
    Thanks.

    Hi Russ,
    Tap Settings in the Home screen then Safari / Clear Cache - Cookies and History.
    Restart your iPad. Press and hold the Sleep/Wake button until the red slider appears. Slide your finger across the slider to turn off iPad. To turn iPad back on, press and hold the Sleep/Wake until the Apple logo appears.
    Hopefully that will kill two birds with one stone.
    Carolyn

  • Site CSS cache error in DW

    The probelm is : I have added a website A in my DW, it is OK. But when I use DW edit any other HTML page from site B, the page review in DW shows the  A site CSS.
    I think it maybe the CSS cache by the site A, How do I clear them?
    Thanks

    Hey Gunter,
    Thanks much, that did work.
    The other error I spoke of was fixed with the new database, so apparently the two errors I spoke of weren't related.
    You seem to be a good help to this forum, thank you for that.... fixing my problem relieved me from much stress.
    Cheers,
    Derek Miller
    Dreamweaver Enthusiast

  • Emptying Safari's Cache?

    Another problem with this disastrous Safari "update" is that as far as I can see you cannot empty safari's cache.  Is this true?   This is truly a terrible update and cannot understand how it even got passed!!!
    Edit.  You apparently have to go to Pref---> Advanced then tick 'Show Develop Menu in Menu Bar'!!! 

    Thanks a bunch for the info! I have taken an AppleScript & assigned it to an Automator Workflow which in turn I've assigned to iCal to schedule for a weekly or monthly emptying of Safari's Cache. Now websites will always load as they should!
    Thanks for your help!
    Nate

  • Safari's caches

    Hello,
    This is hope above experience: does anyone know a way to empty Safari's caches from the
    command line?
    Big-big thanks if you can find a way,
    Mike

    Dear Folks,
    Thank you for the info. I deleted whatever you suggested and Safari did not stop working
    I am sorry that I did not answer you earlier. I did not know that notifications went to my .mac account and it seemed that nobody answered my question.
    Every version of OSX seems to be bigger and bigger.
    Dutch, French, ..., Spanish.lproj are in huge numbers, each group has some 3-6000 files.
    I have one hp printer but I got some 700 MB of files. A lot of culling is awaiting ...
    Mike

  • The Size or Non-Size of Safari's Cache

    Greetings:
    I know this question's been asked ad nuseum here and only because the answers back are more inscrutable than a Chinese crossword puzzle, which is bad enough, then you even get the "well, why do you even wanna do that??" Because I want to! Why don't Firefox and Omniweb users ever get the same silly replies? Sorry if I sound surly, but it's REALLY just a pair of simple Q&As: All I wish to know is 1.) How large is Safari's cache if it's size is non-adjustable and 2.) if it can be adjusted then how do you do it? That's all. On a separate note, I'd be using Safari exclusively if it just offered off-line reading of cached pages like iCab and Firefox.
    Thanks all,
    James Greenidge
    Using Safari 3.04 on 1.25gig eMac 10.4.11

    Which cache? There are several. They are set internally by Safari and not under user control, so it's not possible to know how much disk space the caches could consume. My guess would be around 10 MBs.

  • CSS & Cache Engine

    Guys,
    Dose anybody know any good books or refrece material or notes on Cisco CSS & Cache Engines which can help me to understand the product as well as help me to configure and troubleshoot?
    Thanks,
    Rits

    Check on www.ciscopress.com
    Some good Cisco engineers wrote the following book:
    "Designing Content Switching Solutions"
    I didn't read it myself [don't really need to ;-)] but the engineers who wrote the book have been working with css, cache and other content networking devices for quite a while now.
    Gilles.

  • Safari iOS 7 bug: not rendering images

    Safari has a bug, it does not render image from The Economist at all:
    http://www.economist.com/node/21586620?fsrc=scn/gp/wl/dc/politicsandpurse
    Same goes for Safari modules that are used by other apps, e.g. Google+.
    Chrome with data compression renders OK, but it does so because data compression goes through Google server, and only decoding is done on machine.
    This all took place on iPad Mini.
    Shame on Apple Inc.

    Hi there,
    I can confirm this bug.
    Not sure if this info is relevant, but this is my experience:
    I am on the FIDO network, and so are two other people I know.
    We all tried blocking numbers, and calls ring right through. Text messages are blocked successfully. (never tried facetime)
    I also tried a ROGERS device running IOS7, and was successfully able to block my phone call from ringing through. HOWEVER, my call was forwarded to their voicemail, I was able to leave a voicemail for the person, and they did get an alert that they had a new voicemail.
    I have not yet had a chance to test this on Bell, Telus, or any other carriers.
    Spoke to Apple, and they advised me to do a hard reset (hold both buttons to shut off and reboot the phone), and if that fails to do an iOS restore.
    I have yet to try this, but hopefully someone will have a better solution.

  • Why can't Safari's Download URLs see Safari's cache?

    You'd think that the typical pattern for this action is something like..
    browse to a web site, like what you see, want to import into iphoto
    but when I do that over dialup it wants to redownload every url I give to Download URLs. These urls are images and they are already in Safari's cache. It would be nice if automator actions that operate on content available to Safari could consulate Safari's cache. That way this Download URLs action wouldn't timeout each and everytime I use it.

    Maybe I'm missing something, but where exactly do you see Download URLs in Safari?

  • Does Safari have a bug ?? December 06, 2006

    For the past week it appears that Safari is getting sicker. Web pages I have viewed a thousand times are now not loading. I haven't been able to get onto google in at least a week. Images are not being displayed on other sites and sites that do load take a while. also the server for my mail times out ?? I have deleted cookies, reset safari, emptied cache ... so what do I do now ?? anyone else having the same problems ??

    I think you issue maybe with the security update that was issued last week.
    Whenever I try and change my Top Friends, the page just hangs. The problem occurs when I try and navigate to page 2 - 8 of my friends. the page hangs then gives me the following error message:
    Safari could not open the page “http://editprofile.myspace.com/index.cfm?fuseaction=user.editTopFriends&UserName =++++++++++(REPLACED BY POSTER)+REPLACED BY POSTER+REPLACED BY POSTER)
    &f_search=&searchby=first&page=1&finalpage=&prevPage=0&lastpage=0&PREVPageLASTON ERETURENED=3412006&PREVPageFirstONERETURENED=14061&TotalRecords=301&
    myTopFriends=51630402%2
    C21340095%2C65886561%2C77950793%2C3497846%2C749668%2C116086148%2C46411252%2C7498
    5218%2C563624%2C26224531%2C24373698%2C356
    62885%2C43284317%2C22053298%2C14907883%2C110936497%
    2C22186704%2C16078732%2C88426198%2C37420230%2C37386493%2C55377667%2C571973&topNu mber=24” because the server stopped responding.
    Also, my page was completely jumbled as well (went thru the pain of re-doing the page... but haven't seem to have an issue since).
    I'm also have issue on other sites (mainly messageboards) which I think is Java Script related. In most cases the page hang at 'completed 6 of 7 items' (when viewing the activity window it reads:
    http://www.burstnet.com/cgi-bin/ads/ad10031b.cgi/v=2.0S/sz=468x60A/88471/NI/RETU RN-CODE/JS/ 0 bytes of ?). After a minute or two it times out (activity window says Timed Out) and the page appears (of course the ad is missing)
    This issued started at the same time as the myspace issue.
    And yes, I did the security update last week, that's when i started having issues...
    Lastly ,this is happening on BonEcho (Firefox 2.0) as well, which mean it may not be just Safari. Can anybody verify? Any solutions?
    Judging by the number of people posting issues with Safari (which a lot seem to be similar in nature) since the security update, we are not alone...
    iMac   Mac OS X (10.4.8)  

Maybe you are looking for