Page is always displayed from cache with old data even refresh button is pressed and new content is available

RESOLVED WORKSFORME

Status

()

RESOLVED WORKSFORME
14 years ago
14 years ago

People

(Reporter: drinsoft, Unassigned)

Tracking

1.0 Branch
x86
Windows XP
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

14 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; it-IT; rv:1.7.7) Gecko/20050414 Firefox/1.0.3
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; it-IT; rv:1.7.7) Gecko/20050414 Firefox/1.0.3

The site at URL "http://www.beppegrillo.it" is an italian blog, which is
frequently updated. I ran Firefox in a computer connected to a network, thru a
firewall which uses Wingate v. 6, on Windows 2000 Server.
The problem is that the page is always displayed from cache with old data even
refresh button is pressed and new content is available.
Actually I solved the problem by accessing the blog with Internet Explorer, then
pushing the refresh button, then new data are loaded.
From that moment onwards, Firefox too shows new data by pressing the refresh button.


Reproducible: Always

Steps to Reproduce:
1. Open Firefox and go to URL www.beppegrillo.it
2. Push Firefox refresh button
3. Open Internet explorer and go to URL www.beppegrillo.it 
4. Push Internet Explorer refresh button
5. See that the browser shows new data than Firefox.



Expected Results:  
It seems that Firefox do not really send the request of update to Wingate engine
while the refresh button is pressed, so the old data is still showed.

Comment 1

14 years ago
You probably need to check the FAQ sheet and other troubleshooting resources
for Firefox.

Does shift refresh do what you want?

Having said that, your page does send correct Expires and Modified headers.
My Firefox sends this request for a plain refresh:

	GET http://www.beppegrillo.it/ HTTP/1.1
	Host: www.beppegrillo.it
	User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8b2)
Gecko/20050511 Firefox/1.0+
	Accept:
text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
	Accept-Language: en-us,en;q=0.5
	Accept-Encoding: gzip,deflate
	Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
	Keep-Alive: 300
	Proxy-Connection: keep-alive
	If-Modified-Since: Thu, 12 May 2005 05:37:43 GMT
	If-None-Match: "4f5865-c61a-4282eba7"
	Cache-Control: max-age=0

which looks 100% correct to me. Are you  sure that your proxy properly
understands HTTP 1.1, and that it is sending an IMS request.

Is the data you are seeing coming from Firefox's cache or Wingate's
cache?

Does your proxy send X-Cache headers which might help you diagnose the
problem?

If there is a problem with wingate, then it should be docuemnted, and perhaps
Firefox should warn ...
(Reporter)

Comment 2

14 years ago
(In reply to comment #1)
> You probably need to check the FAQ sheet and other troubleshooting resources
> for Firefox.
> 
> Does shift refresh do what you want?
> 
> Having said that, your page does send correct Expires and Modified headers.
> My Firefox sends this request for a plain refresh:
> 
> 	GET http://www.beppegrillo.it/ HTTP/1.1
> 	Host: www.beppegrillo.it
> 	User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8b2)
> Gecko/20050511 Firefox/1.0+
> 	Accept:
>
text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
> 	Accept-Language: en-us,en;q=0.5
> 	Accept-Encoding: gzip,deflate
> 	Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
> 	Keep-Alive: 300
> 	Proxy-Connection: keep-alive
> 	If-Modified-Since: Thu, 12 May 2005 05:37:43 GMT
> 	If-None-Match: "4f5865-c61a-4282eba7"
> 	Cache-Control: max-age=0
> 
> which looks 100% correct to me. Are you  sure that your proxy properly
> understands HTTP 1.1, and that it is sending an IMS request.
> 
> Is the data you are seeing coming from Firefox's cache or Wingate's
> cache?
> 
> Does your proxy send X-Cache headers which might help you diagnose the
> problem?
> 
> If there is a problem with wingate, then it should be docuemnted, and perhaps
> Firefox should warn ...

Yes, shift refresh solved the problem!
Now, what's the difference between simply refresh and shift refresh?

Thanks in advance for your advice!
Best Regards
Campanelli Paolo
Status: UNCONFIRMED → RESOLVED
Last Resolved: 14 years ago
Resolution: --- → FIXED

Updated

14 years ago
Status: RESOLVED → UNCONFIRMED
Resolution: FIXED → ---
Version: unspecified → 1.0 Branch

Updated

14 years ago
Status: UNCONFIRMED → RESOLVED
Last Resolved: 14 years ago14 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.