Sorry, "www instead of http" is total nonsense. They are different things, not replaceable: "http" or "https" is the
scheme and "www" is the part of the
host, the part "www" itself normally represents the lowest-level
subdomain, which traditionally plays the special role, in particular, the domain with "www." is typically mapped to the same name without "www.". Please see:
Uniform Resource Identifier — Wikipedia, the free encyclopedia[
^],
World Wide Web — Wikipedia, the free encyclopedia[
^],
Domain name — Wikipedia, the free encyclopedia[
^],
Subdomain — Wikipedia, the free encyclopedia[
^].
This matter has nothing to do with the notion of "relative URL". For the
file scheme of URI, the syntax of the
path part of the URI (
Uniform Resource Locator — Wikipedia, the free encyclopedia[
^]) closely follows traditional "UNIX-like" syntax of file paths. Relative paths starts with '.' (current sub-directory), '..' (parent sub-directory) or the simple name of the immediate child of a current directory; this part is optionally followed by the
directory separator '/' (even on Microsoft systems confusingly using backslash) and the rest of the sub-directory structure. For example: "child-of-current-directory/grandchild", "../peer/child", "./child-of-current-directory/grandchild".
Note that the URI can be
protocol-relative:
Uniform Resource Locator — Wikipedia, the free encyclopedia[
^].
So, practically, how to navigate to "www.*"? There is no such thing. Most likely, it's either "http://www.*" or "https://www.*". (Unless you confusingly created a local file system directory using this naming style, but then the answer is quite obvious.) This will be the absolute URI.
—SA