System: WinNT SP5 on PII 400 with 64 MB RAM. Build: Mozilla 1999112508. Overview: Reload is not working properly (at least through proxy). Pressing the <Reload> button fetches the document from the proxy cache instead of directly from the server. Test Case: Open Mozilla, NS4.x, IE5 from the same machine. Set them up so that they pass through a proxy. Set proxy access loggin on. Load http://mozilla.org in all three windows. Now press <Reload> in all three and monitor the proxy access log. This is what you get: From Mozilla 1999112508: ------------------------- 943883898.617 23 172.18.16.56 TCP_HIT/200 10824 GET http://www.mozilla.org/ - NONE/- text/html From IE5: ---------- 943883995.990 2305 172.18.16.56 TCP_MISS/304 137 GET http://www.mozilla.org/ - DIRECT/www.mozilla.org - 943883998.840 2802 172.18.16.56 TCP_MISS/304 137 GET http://www.mozilla.org/images/mozilla-banner.gif - DIRECT/www.mozilla.org - From NS4.7: ------------ 943884085.187 2450 172.18.16.56 TCP_MISS/304 137 GET http://www.mozilla.org/ - DIRECT/www.mozilla.org - 943884088.668 3479 172.18.16.56 TCP_MISS/304 178 GET http://www.mozilla.org/images/mozilla-banner.gif - DIRECT/www.mozilla.org - So, Mozilla is loading the document from the proxy cache while the others are requesting direct transfer from the server (correctly, since <Reload> should fetch from the server directly and not from the cache). Proxy Used for testing: Squid 2.0Patch2 on AIX (compiled from source).

I am getting some strange behaviour - it seems to work at times. But the bug is definitely there since updating a page in my site and hitting <Reload> from Mozilla is getting the old page. Again, all this through proxy. Apropos of this, another small bug - the network preference in all.js for do-not-use-proxy- for does not work. Filing another bug for this.

Reassigning all of leger's unscreened Browser-General bugs to nobody@mozilla.org for pre-screening and triage.

Moving to "Networking" Component from "Browser-General" tever@netscape.com, I've read 30+ bug reports looking for one that this is a DUP of, but no other bug report involves both proxies and reloads... this looks like a new issue.

Depends on hooking up the buttons to pass the right load flags.

PDT+

Cache needs to set "Pragma: no-cache" on the outbound request for clean reloads. assigning to cache men.

This depends on a m15 bug( 21137) being fixed. Do we need to fix that one for beta also?

more like a depends on instead of dup but with 14772 fixed this will be too. Marking as dup... *** This bug has been marked as a duplicate of 14772 ***

verified dupe 14772