| Age | Commit message (Collapse) | Author | 
|---|
|  |  | 
|  |  | 
|  | Path may also have colon, so make sure we don't scan
into the path element if there is one. | 
|  | * Detect bad characters in host names.
* Incorporate splitting host and port into the state
  machine that is parsing/decoding the host.
NOTE:
    IPv6address is not checked for bad characters yet.
    More research is needed to learn exactly what are
    the various ways to write an IPv6 address. | 
|  | A colon may be in the authority, if present, so limit
the search for scheme delimiter so we aren't scanning
the authority part, when parsing the scheme. | 
|  |  | 
|  |  | 
|  |  | 
|  | * Add IsRelativeReference.
* Add IsRelativePath.
* Add Query.
* Add Fragment.
* Add UserInfo.
* Fix parsing of URIs that have no scheme. | 
|  |  | 
|  | * Parts of a path are called "segments", not "steps",
  in the RFC.
* The RFC specifies that path separators are always
  forward slashes, so don't support other separators. | 
|  | * Can now parse URIs from strings.
* This supports scheme, host, and path.
* Path separator defaults to "/" but may be customized. | 
|  |  |