281754 - HTTP 302 redirect doesn't show the new location if the page containing the item to be redirected has been viewed before

Status: VERIFIED DUPLICATE of bug 89419

(Firefox :: General, defect)

Description

[Chua Chee Wee]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0

1. I visit a particular webpage which contains a reference to an image, say, at
http://chuacw.hn.org/images/chuacw_hn_org/chewy/57/r_Gee+Gee+crying+2.jpg

2. Since I'm the author and web master of chuacw.hn.org, I updated my own code
so that references to the above image causes a HTTP 302 Redirect to another
location, say, http://www.spilogsjov.dk/missb/fat-woman.jpg

3. However, if I click refresh in the browser, I'm still seeing the original
image in 1, instead of the image in 2.

4. If I close the browser and revisit the page in 1, then I see the new image in 2.

5. What I'm expecting is, without closing the browser, when I click refresh, I
should see the new image in 2.

Reproducible: Always

Steps to Reproduce:
1. Create a webpage on a server such that the webpage contains an image A.
2. View the webpage using Firefox.
3. Update the server such that viewing image A issues a HTTP 302 sending the
user to image B.
4. Click refresh in Firefox.
Actual Results:  
I still see image A.

Expected Results:  
What I'm expecting is, without closing the browser, when I click refresh, I
should see the image B.

When I click refresh in Firefox, I already see that the server is sending HTTP
302, redirecting the browser to go to another location.

Yet, in Firefox, I still see the original image (eg, Image A) being displayed,
instead of image B.

Comment 1

[:Gavin Sharp [email: [e-mail]]]

You have to use Shift+Reload to force a refresh, otherwise Firefox caches
images. This is likely INVALID.

Comment 2

[Chua Chee Wee]

(In reply to comment #1)
> You have to use Shift+Reload to force a refresh, otherwise Firefox caches
> images. This is likely INVALID.

What is likely INVALID? My report? Or pressing Shift Reload to force a refresh?

If Firefox is caching images, why does it still send a HTTP GET "Image A" to the
server? If Firefox is caching images, I would be expecting not to see HTTP GET
"Image A" to the server, but it still does. So, something is broken somewhere.

And also, since Firefox is sending HTTP GET "Image A" to the server, it is not
honouring the response, since the response is a HTTP 302 redirect.

Comment 3

[WADA:World Anti-bad-Duping Agency]

Reporter, isn't it same as Bug 281486?
If yes, possibly DUP of Bug 89419.
(But I can't say Bug 281486 is DUP of Bug 89419, then reported problem to Bug
281486.)
Easiest workaround in this case is Shift+Reload, as Gavin Sharp says. 

By the way, many of components are shared by Mozilla & Firefox, Mozilla &
Thunderbird, and common component's Product are set to Core, Toolkit and so on,
according to recent Product/Component structure change.
Reporter, search bugs with Product=Core, Toolkit etc. also before open bug, please.
  

Comment 4

[WADA:World Anti-bad-Duping Agency]

Another workaround is update timestamp of Image-B at server side.
If Image-B's timestamp is greater than one in client's cache, Mozilla will
download it again and cache information is updated correctly on "Reload", then
newly re-directed Image-B will be used.

Comment 5

[Boris Zbarsky [:bzbarsky]]

*** This bug has been marked as a duplicate of 89419 ***