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
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar

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
  • #3709

Closed
Open
Opened Aug 10, 2011 by Karsten Loesing@karsten

Handle non-integer values in fields marked as integers better

George reports:

For a small issue, if you go to the advanced search page and give a non-integer value to fields marked as integers - like orport, dirport, bandwidth or uptime - you get django's debugging page, which fortunately doesn't contain super-sensitive information.

We turned off the Debug mode, so there's no debugging page anymore. But now we only get an empty page in the error case. There should be some output saying that only integers are allowed in those fields. More generally, we should make sure that we check all input very carefully.

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