Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • S sbws
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 5
    • Issues 5
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Network Health
  • sbws
  • Issues
  • #28741
Closed
Open
Created 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.

Assignee
Assign to
Time tracking