Back to index
URIs are essentially structured names for things -- anything. More...
|boolean||equals (in nsIURI other)|
|URI equivalence test (not a strict string comparison). |
|boolean||schemeIs (in string scheme)|
|An optimization to do scheme checks without requiring the users of nsIURI to GetScheme, thereby saving extra allocating and freeing. |
|Clones the current URI. |
|AUTF8String||resolve (in AUTF8String relativePath)|
|This method resolves a relative string into an absolute URI string, using this URI as the base. |
|Returns a string representation of the URI. |
|readonly attribute AUTF8String||prePath|
|The prePath (eg. |
|The Scheme is the protocol to which this URI refers. |
|The username:password (or username only if value doesn't contain a ':') |
|The optional username and password, assuming the preHost consists of username:password. |
|The host:port (or simply the host, if port == -1). |
|The host is the internet domain name to which this URI refers. |
|A port value of -1 corresponds to the protocol's default port (eg. |
|The path, typically including at least a leading '/' (but may also be empty, depending on the protocol). |
|readonly attribute ACString||asciiSpec|
|The URI spec with an ASCII compatible encoding. |
|readonly attribute ACString||asciiHost|
|The URI host with an ASCII compatible encoding. |
|readonly attribute ACString||originCharset|
|The charset of the document from which this URI originated. |
URIs are essentially structured names for things -- anything.
This interface provides accessors to set and query the most basic components of an URI. Subclasses, including nsIURL, impose greater structure on the URI.
This interface follows Tim Berners-Lee's URI spec (RFC2396) , where the basic URI components are defined as such:
ftp://username:password@hostname:portnumber/pathname \ / \ / \ / \ /\ / - --------------- ------ -------- ------- | | | | | | | | | Path | | | Port | | Host / | UserPass / Scheme / \ / -------------------------------- | PrePath
The definition of the URI components has been extended to allow for internationalized domain names  and the more generic IRI structure .
 http://www.ietf.org/rfc/rfc2396.txt  http://www.ietf.org/internet-drafts/draft-ietf-idn-idna-06.txt  http://www.ietf.org/internet-drafts/draft-masinter-url-i18n-08.txt nsIURI - interface for an uniform resource identifier w/ i18n support.
AUTF8String attributes may contain unescaped UTF-8 characters. Consumers should be careful to escape the UTF-8 strings as necessary, but should always try to "display" the UTF-8 version as provided by this interface.
AUTF8String attributes may also contain escaped characters.
Unescaping URI segments is unadvised unless there is intimate knowledge of the underlying charset or there is no plan to display (or otherwise enforce a charset on) the resulting URI substring.
Clones the current URI.
For some protocols, this is more than just an optimization. For example, under MacOS, the spec of a file URL does not necessarily uniquely identify a file since two volumes could share the same name.
This method resolves a relative string into an absolute URI string, using this URI as the base.
NOTE: some implementations may have no concept of a relative URI.
An optimization to do scheme checks without requiring the users of nsIURI to GetScheme, thereby saving extra allocating and freeing.
Returns true if the schemes match (case ignored).
The charset of the document from which this URI originated.
An empty value implies UTF-8.
If this value is something other than UTF-8 then the URI components (e.g., spec, prePath, username, etc.) will all be fully URL-escaped. Otherwise, the URI components may contain unescaped multibyte UTF-8 characters.