Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Issues
  • #15733

Closed (moved)
Open
Opened Apr 19, 2015 by Arthur Edelstein@arthuredelstein

ftp pages are not isolated in the cache

I noticed that if I load http://arthuredelstein.github.io/tordemos/ftp-in-iframe.html and http://arthurtordemos.github.io/tordemos/ftp-in-iframe.html in two different tabs.

Then I can see that the ftp document, ftp://ftp.mozilla.org/pub/mozilla.org/ in about:cache. It says "Fetch count: 2" and "No expiration time."

The behavior is inconsistent. Sometimes it looks as though there is only one network fetch, and sometimes two. Also, the ftp page sometimes disappears from the cache after a short while, which makes me think "no expiration time" means "expires pretty soon". The quick expiration means this is likely not a great linking vector, but I guess it's probably better to key ftp page caching by url bar domain.

To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#15733