36 * Locator, a pointer to a "resource" on the World |
36 * Locator, a pointer to a "resource" on the World |
37 * Wide Web. A resource can be something as simple as a file or a |
37 * Wide Web. A resource can be something as simple as a file or a |
38 * directory, or it can be a reference to a more complicated object, |
38 * directory, or it can be a reference to a more complicated object, |
39 * such as a query to a database or to a search engine. More |
39 * such as a query to a database or to a search engine. More |
40 * information on the types of URLs and their formats can be found at: |
40 * information on the types of URLs and their formats can be found at: |
41 * <blockquote> |
41 * <a href= |
42 * <a href="http://www.socs.uts.edu.au/MosaicDocs-old/url-primer.html"> |
42 * "http://web.archive.org/web/20051219043731/http://archive.ncsa.uiuc.edu/SDG/Software/Mosaic/Demo/url-primer.html"> |
43 * <i>http://www.socs.uts.edu.au/MosaicDocs-old/url-primer.html</i></a> |
43 * <i>Types of URL</i></a> |
44 * </blockquote> |
|
45 * <p> |
44 * <p> |
46 * In general, a URL can be broken into several parts. The previous |
45 * In general, a URL can be broken into several parts. Consider the |
47 * example of a URL indicates that the protocol to use is |
46 * following example: |
|
47 * <blockquote><pre> |
|
48 * http://www.example.com/docs/resource1.html |
|
49 * </pre></blockquote> |
|
50 * <p> |
|
51 * The URL above indicates that the protocol to use is |
48 * <code>http</code> (HyperText Transfer Protocol) and that the |
52 * <code>http</code> (HyperText Transfer Protocol) and that the |
49 * information resides on a host machine named |
53 * information resides on a host machine named |
50 * <code>www.socs.uts.edu.au</code>. The information on that host |
54 * <code>www.example.com</code>. The information on that host |
51 * machine is named <code>/MosaicDocs-old/url-primer.html</code>. The exact |
55 * machine is named <code>/docs/resource1.html</code>. The exact |
52 * meaning of this name on the host machine is both protocol |
56 * meaning of this name on the host machine is both protocol |
53 * dependent and host dependent. The information normally resides in |
57 * dependent and host dependent. The information normally resides in |
54 * a file, but it could be generated on the fly. This component of |
58 * a file, but it could be generated on the fly. This component of |
55 * the URL is called the <i>path</i> component. |
59 * the URL is called the <i>path</i> component. |
56 * <p> |
60 * <p> |
59 * machine. If the port is not specified, the default port for |
63 * machine. If the port is not specified, the default port for |
60 * the protocol is used instead. For example, the default port for |
64 * the protocol is used instead. For example, the default port for |
61 * <code>http</code> is <code>80</code>. An alternative port could be |
65 * <code>http</code> is <code>80</code>. An alternative port could be |
62 * specified as: |
66 * specified as: |
63 * <blockquote><pre> |
67 * <blockquote><pre> |
64 * http://www.socs.uts.edu.au:80/MosaicDocs-old/url-primer.html |
68 * http://www.example.com:1080/docs/resource1.html |
65 * </pre></blockquote> |
69 * </pre></blockquote> |
66 * <p> |
70 * <p> |
67 * The syntax of <code>URL</code> is defined by <a |
71 * The syntax of <code>URL</code> is defined by <a |
68 * href="http://www.ietf.org/rfc/rfc2396.txt"><i>RFC 2396: Uniform |
72 * href="http://www.ietf.org/rfc/rfc2396.txt"><i>RFC 2396: Uniform |
69 * Resource Identifiers (URI): Generic Syntax</i></a>, amended by <a |
73 * Resource Identifiers (URI): Generic Syntax</i></a>, amended by <a |