"Source" in Page Info lies (almost always says "Disk Cache")

RESOLVED INVALID

Status

SeaMonkey
Page Info
--
major
RESOLVED INVALID
17 years ago
9 years ago

People

(Reporter: Jesse Ruderman, Assigned: db48x)

Tracking

Trunk
x86
Windows 98

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

17 years ago
Steps to reproduce:
1. Go to a random page you haven't been to before (without a ? in the URL).
2. Ctrl+I.

Result: Page Info says "Source: Disk Cache"
Expected: "Source: Web"

It would be nice if the sources included reasons:
 Source: Web (wasn't in cache)
 Source: Web (cached version had expired)
 Source: Web (cached version failed validation)
 Source: Cache (validated freshness through Web)
 Source: Cache (hasn't expired, didn't check for freshness)
 Source: Cache (expired, but in offline mode)

But the important thing is that Page Info shouldn't lie.
(Assignee)

Comment 1

17 years ago
it doesn't lie, the page really is in the cache. 
(Reporter)

Comment 2

17 years ago
Is the page info entry supposed to say whether the page is cached, or whether
the page displayed came from the cache?
(Assignee)

Comment 3

17 years ago
both :)

if the cache (either memory or disk) is active, the page is downladed, stored in
the cache, and then displayed from the cache. Currently I don't think there is
an easy way to know if mozilla actually had to go out over the network and
download everything, or if it had everything in the cache already, which, I'll
admit, would be more useful than the current implementation. There might be away
to guess though. I'll check.
(Assignee)

Comment 4

17 years ago
no, there doesn't appear to be any way to guess. any ideas?
(Assignee)

Updated

17 years ago
Status: NEW → ASSIGNED
Priority: -- → P3
Target Milestone: --- → mozilla1.1beta
Product: Browser → Seamonkey
Status: ASSIGNED → NEW
Priority: P3 → --
QA Contact: pmac
Target Milestone: mozilla1.1beta → ---

Comment 5

9 years ago
The general tab doesn't show Source: in the current implementation.
Closing as INVALID.
Status: NEW → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.