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

Closed (moved)
Open
Opened Dec 05, 2018 by teor@teor

sbws should send scanner metadata as part of every HTTP request

We can't find out which torflow instances are using a bandwidth server: https://lists.torproject.org/pipermail/tor-project/2018-December/002108.html

As far as I can tell, sbws doesn't provide any scanner info in its HTTP requests.

Here's some things we might want:

  • software-name: sbws
  • software-version
  • scanner-nickname
  • scanner-IP-address? (pro: doscover users who haven't set nickname, con: discover users)

Non-standard HTTP headers start with "X-".

Assigning to 1.0, because this is vital debugging info.

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