Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • 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
  • #33385

Project 'torproject/web/tpo' was moved to 'tpo/web/tpo'. Please update any links and bookmarks that may still have the old path.
Closed (moved)
(moved)
Open
Created Feb 19, 2020 by David Fifield@dcf

In server, treat a purported client IP address of 0.0.0.0 as missing

In #33157 (moved), proxies sometimes fail to extract a meaningful client IP address from the client's SDP and send ?client_ip=0.0.0.0 to the bridge. The bridge counts an address of 0.0.0.0 as a client that had an IP address, which inflates the numerator in the "in the past %.f s, %d/%d connections had client_ip" log line.

This is a patch to treat a client address of 0.0.0.0 or [::] as if it were not present at all.

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