Supported URLs


Supported URLs
**************

   ::WORK:: List supported URL types, specific RFCs, etc.

   "Uniform Resource Locators" (URLs) are a specific form of "Uniform
Resource Identifiers" (URI) described in RFC2396 which updates RFC1738
and RFC1808.

   RFC2016 defines uniform resource agents.

   URI have the form SCHEME:SCHEME-SPECIFIC-PART, where SCHEME appears
in the menu below for URLs supported by Emacs/W3.

   FTP, NFS, HTTP, HTTPS, `rlogin', `telnet', tn3270, IRC and gopher
URLs all have the form SCHEME://[USERINFO@]HOSTNAME[:PORT][/PATH] where
`[' and `]' delimit optional parts.  USERINFO sometimes takes the form
USERINFO:PASSWORD but you should beware of the security risks of
sending cleartext passwords.  HOSTNAME may be a domain name or a dotted
decimal address.  If the `:PORT' is omitted then Emacs/W3 will use the
well known port for that service.  With the possible exception of
`telnet', it is very rare for ports to be specified, and it is possible
using a non-standard port may have undesired consequences if a
different service is listening on that port (eg. a gopher URL
specifying the SMTP port can cause mail to be sent), but *Note
url-bad-port-list: Other Variables.  The meaning of the PATH component
depends on the service.

file: Local file access.
ftp: Remote file access via ftp.
nfs: Remote file access via NFS.
info: Access to the Emacs Info system.
http/https: HTTP/1.0 support.
mailto: Sending simple electronic mail.
mailserver: Slightly more complicated electronic mail.
news/nntp/snews: Reading and sending Usenet news.
rlogin/telnet/tn3270: Legacy host connections.
irc: Internet Relay Chat.
data: Embedding the data within the URL itself.
gopher: Gopher and Gopher+.
finger: The old favorite.
netrek: netrek.

Menu