up vote 1 down vote favorite
share [g+] share [fb]

So, I broke a website with some server changes oops. I roll back the changes I made, hit cmd-R, and oh noes, it is still broken. But I relax thinking, there must be something held in safari's cache so I press the handy 'Empty Cache' button. Hit cmd-R for refresh it is still broken. I'm really worried that I've done it and broken something bigtime. But first decide to check on a hand win xp computer, and voila it works.

So the question is how do you "really" clear the cache w/o restart safari, I have many browser windows open a restart every time I make a server side change will ruin me.

Any suggestions? Thanks!

link|improve this question
feedback

1 Answer

up vote 0 down vote

Any chance the problem was due to a cookie and not a cached file?

link|improve this answer
Negative, unless 500 internal server error uses a cookie ;) – Mitch May 12 '10 at 23:05
@Mitch I'll bet you've got a cookie on that client that something on the server side is choking on, causing the 500 error. How could it ever possibly make sense for a browser to cache a 500 error? Or are you saying that you're specifically testing your server's 500 error page, and Safari keeps showing you an old version of that page? – Spiff May 13 '10 at 19:54
Sry 4 long comment! No, its crashing on the "frontpage" of a joomla website, there is no cookie deployed there. Even if there was, how could it be served if the virtual host is dying with a 500. Furthermore, I know exactly what caused the server to choke some malformed config files, but after I fixed it and restarted the server the 500 error persisted despite successfully serving pages on a different computer. Re: how could it make sense for a browser cache a 500 error, windows caches dns misses as well its not so different. Safari is definitely caching a 500 error. – Mitch May 13 '10 at 20:32
@Mitch can you still reproduce the problem? If so, run sudo tcpdump -nAs0 port 80 | grep HTTP, then reload the page, and look at all the response codes you get back, so you can see whether or not you're really getting a 500. If you ARE getting a 500 back, then you can run that tcpdump command without piping it through grep and you can look at all of the request and response headers to see what's going on. – Spiff May 14 '10 at 1:43
feedback

Your Answer

 
or
required, but never shown
discard

Not the answer you're looking for? Browse other questions tagged or ask your own question.