I had a similar problem with caching; I would make a byte-range
request for a URL; the next request for that url, even a different
byte-range (or a request for the entire thing) would return 206 (or
200) with the original byte-range contents.
I solved it by changing the user-agent in the request, since caching
is keyed off user-agent as well as URL. Perhaps you can have two
different user-agents, one for the the webViews for which you want
the image, and one where you don't.
Rudi
On Dec 12, 2005, at 2:58 AM, Manfred Schwind wrote:
I think this is a bug in WebKit. I suspect that it's the WebCore
cache that's causing the trouble. It would be great if you could
file a bug report, especially if you could provide a test
application to use to reproduce it.
Okay.
You may have better luck if you use -[WebPreferences
setLoadsImagesAutomatically:NO] on your hidden web views. You can
set per-WebView preferences, and I think that works fine.
No, it makes no difference. The same problem: if webView1 is
configured to setLoadsImagesAutomatically:NO and webView2 is
configured to setLoadsImagesAutomatically:YES and both webViews
refer the same image from their HTML, the image is not loaded in
both webViews (if webView1 is loaded first).
If webView1 is also configured to setLoadsImagesAutomatically:YES,
then the image loads fine in both webViews.
<rdar://4375379>
Bye,
Mani
_______________________________________________
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/rsherry%
40adobe.com
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
