Closed Bug 394550 Opened 17 years ago Closed 8 years ago

FTP dir listing uses data from cache

Categories

(Core Graveyard :: Networking: FTP, defect, P2)

x86
Windows XP
defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: Paenglab, Unassigned)

References

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a8pre) Gecko/2007083115 Minefield/3.0a8pre
Build Identifier: 

After the checkin for bug 294800, the dir listing uses data from cache. If I go for example to ftp://ftp.eu.mozilla.org/pub/mozilla.org/firefox/tinderbox-builds/ the Last modified time and date aren't updated. Only after a reload I receive the actual modify date.
It looks like all data comes from cache. I think FTP/File/Jar/Gopher dir listings shoulden't be cached.

Reproducible: Always

Steps to Reproduce:
1. Go to a ftp://ftp site witch uptates frequently
2. revisit this site after 1 hour
3. check the modify dates
4. press refresh
5. check the modify dates again
Actual Results:  
Only after step 4 the modify dates are the actuals


Expected Results:  
The modify dates are by every visit the actuals
Confirming.
Tested on ftp://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-trunk-l10n/

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; sk; rv:1.9a8pre) Gecko/2007090604 Minefield/3.0a8pre
Confirming bug based on comment 1. However, I don't know how bug 294800 could have caused this. Is this really a regression?
Blocks: 294800
Status: UNCONFIRMED → NEW
Ever confirmed: true
Whiteboard: regression?
Version: unspecified → Trunk
Keywords: qawanted
I still see this with latest nightlies
Mozilla/5.0 (Windows; U; Windows NT 6.0; sk; rv:1.9b3pre) Gecko/2008013004 Minefield/3.0b3pre
Blocker?
Flags: blocking1.9?
Flags: blocking1.9? → blocking1.9+
Priority: -- → P2
Assignee: nobody → sayrer
Flags: tracking1.9+ → blocking1.9+
we always cached FTP dir listings...
No longer blocks: 294800
Keywords: qawanted
Summary: Beautified FTP dir listing uses data from cache → FTP dir listing uses data from cache
Whiteboard: regression?
then this isn't blocking, renom just in case
Flags: blocking1.9+ → blocking1.9?
Not blocking per comment 5.
Flags: blocking1.9? → blocking1.9-
Assignee: sayrer → nobody
Status: NEW → RESOLVED
Closed: 8 years ago
Component: Networking → Networking: FTP
Resolution: --- → WONTFIX
Actually this is fixed by bug 913827.
Resolution: WONTFIX → FIXED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.