Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #3717
Closed
Open
Issue created Aug 10, 2011 by cypherpunks@cypherpunks

Decide on appropriate mechanism to save current search filters

Currently, TorStatus requires cookies to be enabled, which are used only to store hashed sessionIDs that map to encrypted search preferences that are stored on the TorStatus server. Many users have cookies disabled, however. We should provide functionality to these users.

Some Django programmers have written middleware that passes the sessionID as a GET to the controller if the client has cookies disabled. This doesn't seem to be any more secure than simply enabling cookies for the TorStatus website, however.

It'd be nice to hear what everyone thinks about the mechanism that is currently being used to store search preferences. What would be better way to implement this functionality?

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking