Summary: | Need shift-reload functionality (bypassing proxy cache) | ||
---|---|---|---|
Product: | WebKit | Reporter: | scott |
Component: | Page Loading | Assignee: | Nobody <webkit-unassigned> |
Status: | RESOLVED FIXED | ||
Severity: | Enhancement | CC: | ap, ddkilzer, ian, koivisto |
Priority: | P2 | Keywords: | InRadar |
Version: | 417.x | ||
Hardware: | Mac | ||
OS: | OS X 10.4 |
Description
scott
2006-02-21 23:05:03 PST
Are you behind a caching HTTP proxy, by any chance? Sometimes, these are almost completely transparent, so it might be tricky to find out. No, I am not behind a caching proxy at all, as a matter of fact, at one point in time, I was sitting on a LAN to the server and this was still happening. It is still possible that the server itself includes some sort of a proxy (Apache has mod_cache; WebSTAR has something similar, too). You are very right asking how Firefox can change the way Safari deals with something - it cannot, and it can only affect the server and/or the proxy, to the best of my knowledge. A detailed annotated trace made with tcpdump, tcpflow or EtherPeek could perhaps help to pinpoint the problem. Ill see what more data I can get, though I can assure you there is no proxy on web* server, I have it fully disabled. Should be able to get you more detailed data on this though. Turns out that the webserver is holding a cache of the old data, which is where this problem is coming from. Clearing this cache on the webserver and things clear up just fine. So, the question remains, how do you perform a "shift-reload" like what FireFox does, and what is FireFox and other browsers doing under those "super reload" cases? The problem seems to happen on other webservers as well, so for a developer, a simple "super-reload" would work to alleviate this. The related headers are: 1) Firefox, reload: If-Modified-Since: _date_ If-None-Match: _tag_ Cache-Control: <max-age=0> 2) Firefox, shift-reload: Pragma: no-cache Cache-control: no-cache 3) Safari, reload: Doesn't send any conditional or cache control headers. 4) I don't have WinIE here, but Google says it also has shift-refresh; we need to look at its headers, too. So far, sounds like this may require changes to both open-source WebKit and closed source Safari. Could you please also report this to <http://bugreport.apple.com>, mentioning this bug, and then post that problem number here? Done, and thanks, the bug report id is 4455858 Will this report be updated as it progresses, or should I watch the rdar report? Radar is only accessible to Apple employees, so this mostly depends on who gets to fixing the WebKit part of the problem first. And changes to Safari UI can only be requested via Radar. Turns out we've already had bug 5499 filed for plain reload headers; retargeting this one to be specifically about shift-reload. WebCore and (at least) Mac WebKit has shift-reload support now (done under bug 17998). The rest is application level stuff and does not belong here. We have <rdar://problem/6451745> to cover Windows WebKit. Other archs should file separate bugs if they want the functionality. |