|
|
@ -19,7 +19,7 @@ string will not be in the parsed object. Examples are shown for the URL |
|
|
|
|
|
|
|
Example: `'http:'` |
|
|
|
|
|
|
|
* `slashes`: The protocol requires slashes after the colon |
|
|
|
* `slashes`: The protocol requires slashes after the colon. |
|
|
|
|
|
|
|
Example: true or false |
|
|
|
|
|
|
@ -89,14 +89,14 @@ Here's how the formatting process works: |
|
|
|
* The protocols `http`, `https`, `ftp`, `gopher`, `file` will be |
|
|
|
postfixed with `://` (colon-slash-slash). |
|
|
|
* All other protocols `mailto`, `xmpp`, `aim`, `sftp`, `foo`, etc will |
|
|
|
be postfixed with `:` (colon) |
|
|
|
be postfixed with `:` (colon). |
|
|
|
* `slashes` set to `true` if the protocol requires `://` (colon-slash-slash) |
|
|
|
* Only needs to be set for protocols not previously listed as requiring |
|
|
|
slashes, such as `mongodb://localhost:8000/` |
|
|
|
slashes, such as `mongodb://localhost:8000/`. |
|
|
|
* `auth` will be used if present. |
|
|
|
* `hostname` will only be used if `host` is absent. |
|
|
|
* `port` will only be used if `host` is absent. |
|
|
|
* `host` will be used in place of `hostname` and `port` |
|
|
|
* `host` will be used in place of `hostname` and `port`. |
|
|
|
* `pathname` is treated the same with or without the leading `/` (slash). |
|
|
|
* `query` (object; see `querystring`) will only be used if `search` is absent. |
|
|
|
* `search` will be used in place of `query`. |
|
|
|