Opened 5 years ago

Last modified 4 months ago

#15035 new task

URI format for bridges — at Version 1

Reported by: eighthave Owned by: n8fr8
Priority: Medium Milestone:
Component: Applications/Orbot Version:
Severity: Normal Keywords: uri, url, bridge
Cc: brade, mcs, hans@…, gaba, phw Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description (last modified by n8fr8)

Right now, according to @n8fr8, this is the URI format for the bridge URIs:


There is a problem with this format because it doesn't follow the URI RFC so that standard URI parsers won't parse it very well. Adding the // after bridge: makes it a "hierarchical" URI, which means that it has the standard sections of authority, user info, host, port, path, query, and fragment. But the above URI will just stick all of the text in the "authority" part, but that section can't be broken down into the standard parts of the "authority", i.e. user info, host, and port.

To keep the same data format, then this URI should be an "opaque" URI. That just means removing the //. So that makes it like a mailto: URI.

Otherwise, the data could be refactored to fit into the standard parts for a hierarchical URI, then standard URI parsing classes will be able to parse it. For example,,, etc. That would make the URI look something like this:


  • getScheme() would be bridge type
  • getAuthority() would be IP and port number
  • getHost() would be IP
  • getPort() would be port number
  • getPath() would be this thing: 95151988dc29fccb4f610a1c700a1ddf7d5ffbd4
  • then cert=, iat-mode=, etc. would be in the query string

The downside of this approach is that there could only be a single bridge per URI, but maybe that's not so bad.

Child Tickets

Change History (1)

comment:1 Changed 5 years ago by n8fr8

Description: modified (diff)
Note: See TracTickets for help on using tickets.