I believe that you are looking at the wrong Cache API. I suspect that
the API you want to look at is in the Web Foundation framework, not the
cache associated with the backward/forward list.
You can look up the type NSURLRequestCachePolicy in the documentation.
That looks like it will allow you to tailor the caching strategy used
by a given NSURLRequest (most notably the request that you send to your
You might also try looking at the API for NSURLCache and see if that
helps. NSURLCache has a shared cache member which may be where your
image was actually saved off (i.e. in the same Cache space that the
Safari browser is using).
I'm not exactly sure how to get the behavior you are looking for, but I
suspect that looking up those two things might help.
On Tuesday, July 29, 2003, at 03:05 PM, Paul FitzGerald wrote:
I'm confused, again (still).
I've built a super simple Cocoa app where the window contains a webView
and a button.
When the button is clicked I do a loadRequest with a hard coded URL to
my web server. The URL accesses a .jpg file that is constantly updated
from a web cam.
Since the picture is changing I don't want any caching; I want to get
the current picture each time I click the button.
I'm also trying to turn of caching with:
[(WebView *)webView setMaintainsBackForwardList:NO];
[[(WebView *)webView backForwardList] setPageCacheSize:0];
But this doesn't seem to help.
Is the caching that is related to the Forward/Back stuff the only place
caching is managed? Is this the same caching as page caching?
Another thing I tried was to delete the application's cache folder then
run the app. When I loaded the page it came up with an old picture!
Where did the picture come from? My server was never accessed and the
cache folder was gone!