Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
crabgrass
crabgrass
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 63
    • Issues 63
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 2
    • Merge Requests 2
  • Operations
    • Operations
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • liberate
  • crabgrasscrabgrass
  • Issues
  • #173

Closed
Open
Opened Jun 08, 2018 by dgt@dgtMaintainer

Disable browser caching

Going back in browser history still reveals some private content such as the dashboard.

In addition even public content is enriched with private elements when the user is logged in. For example the main menu has drop downs listing the users groups.

To prevent leaking private information on shared browsing sessions we should disable caching for logged in users entirely.

Edited May 03, 2019 by azul
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: liberate/crabgrass#173