This affects only the back/forward cache, which controls caching of
entire web pages so that you can do a "go back" faster. That's not
what's happening here.
The caching that's causing you trouble is the caching done in WebCore.
This cache is not properly expiring things. And this caching happens
before you get a willSendRequest: callback.
This is a bug in WebKit, and I don't know of a workaround. We plan to
fix the WebCore cache expiration in the next Safari update.
<-- snip -->
Could you tell me if this is indeed the (same) bug that is affecting me.
Best regards
Alan Shouls
Hi
I have had some problems posting this to the list - but it seems to
have worked.
I have also tried making copies of the images specified request, so
they are uniquely named on the fly and in the /tmp directory and
changed the response so that it 'points' to them. Still the cache
refuses to release it's grip
Alan
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webkitsdk-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webkitsdk-dev/
email@hidden
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webkitsdk-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webkitsdk-dev/email@hidden