66341 - Document Reloading does not work correctly

Status: RESOLVED WORKSFORME

(Core :: Networking, defect)

Description

[Kevin Rogers]

From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 4.0)
BuildID:    2001010901

If Mozilla already has received a copy of a web page, it should not obtain a 
new copy but use the current copy in its cache. This should be achieved by 
sending the if-modified-since time in the request header.
The server should compare this with the "last modified time". If the client has 
a current copy then the server should return a response containing the "not 
modified" status.

However, Mozilla sents the incorrect time in the header. This forces the server 
to always return a fresh copy of the web page.

Reproducible: Always
Steps to Reproduce:
1. You will need to write software, such as a servlet, to display the "if-
modified-since" time to verifiy whether this is being updated correctly.
2.
3.

Expected Results:  Once it recieved the first copy of a web page it should 
update the "if modified since" time and send the correct value in the next 
request.

Comment 1

[timeless]

i hope this is a dupe

Comment 2

[Kevin Rogers]

Attachment: HTML files and java source code for servlet

Comment 3

[Kevin Rogers]

I have included an attachment that contains a relatively simple test case 
containing 2 HTML files and java source code for a test servlet.

The problem does not appear when a simple URL is reloaded.

The test case contains a frameset that calls up 2 frames. The left hand frame 
is an HTML file that contains 2 links to anchor locations in the right hand 
frame. The right hand frame is generated by the test servlet.

The right hand frame is reloaded when each link is selected for the first time. 
If a link is selected again a reload does not occur. This is because Mozilla 
sets the last modified time based on each anchor location in the target 
document rather than for the complete target document.

This test case has also been tested with IE5. IE5 behaves correctly. It sets 
the last modified time for the complete target document and so it does not 
force a document reload each time a new link is selected in the left hand frame.

Comment 4

[Keyser Sose]

Reporter would you take a look at bug 40867? Is that the same problem your
seeing or not?

Comment 5

[Kevin Rogers]

I don't believe bug 40867 takes this bug into account. The reloading logic in 
Mozilla seems to depend on the document anchor location rather than the 
document as a whole. This facet of the document reloading problem is not 
mentioned in bug 40867.

Comment 6

[Keyser Sose]

I can't find a dupe of this so going ahead and marking NEW, although i may be
wrong or not looking in the right place.

Comment 7

[benc]

sounds potentialy bad, nominiating nsbeta1, mozilla 0.9.2

Comment 8

[Andrew Hagen]

Last post was June 2001: "sounds potentially bad."

Still?

Comment 9

[benc]

probably not, but I'm not exactly focusing on the HTTP/cache bugs right now :)

Comment 10

[Darin Fisher]

-> default owner