Changes between Version 2 and Version 3 of Ticket #15035


Ignore:
Timestamp:
Feb 25, 2015, 9:59:12 PM (4 years ago)
Author:
n8fr8
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #15035 – Description

    v2 v3  
    11Right now, according to @n8fr8, this is the URI format for the bridge URIs:
    22
    3 `bridge://obfs3+xxx.xxx.xxx.xxx
     3bridge://obfs3+99.999.99.999%3A10223+c6fa110ebcd8979b0a57617bf2d6e82bbecd287d+%0A
    44
    55There 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.