2 @setfilename ../../info/url
3 @settitle URL Programmer's Manual
8 @c @setchapternewpage odd
13 %\global\baselineskip 30pt % for printing in double space
15 @dircategory World Wide Web
18 * URL: (url). URL loading package.
22 This file documents the Emacs Lisp URL loading package.
24 Copyright @copyright{} 1993, 1994, 1995, 1996, 1997, 1998, 1999, 2002,
25 2004, 2005, 2006, 2007, 2008, 2009, 2010 Free Software Foundation, Inc.
28 Permission is granted to copy, distribute and/or modify this document
29 under the terms of the GNU Free Documentation License, Version 1.3 or
30 any later version published by the Free Software Foundation; with no
31 Invariant Sections, with the Front-Cover texts being ``A GNU Manual,''
32 and with the Back-Cover Texts as in (a) below. A copy of the license
33 is included in the section entitled ``GNU Free Documentation License''.
35 (a) The FSF's Back-Cover Text is: ``You have the freedom to copy and
36 modify this GNU manual. Buying copies from the FSF supports it in
37 developing GNU and promoting software freedom.''
43 @title URL Programmer's Manual
44 @subtitle First Edition, URL Version 2.0
45 @author William M. Perry @email{wmperry@@gnu.org}
46 @author David Love @email{fx@@gnu.org}
48 @vskip 0pt plus 1filll
62 * Getting Started:: Preparing your program to use URLs.
63 * Retrieving URLs:: How to use this package to retrieve a URL.
64 * Supported URL Types:: Descriptions of URL types currently supported.
65 * Defining New URLs:: How to define a URL loader for a new protocol.
66 * General Facilities:: URLs can be cached, accessed via a gateway
67 and tracked in a history list.
68 * Customization:: Variables you can alter.
69 * GNU Free Documentation License:: The license for this documentation.
76 @chapter Getting Started
77 @cindex URLs, definition
80 @dfn{Uniform Resource Locators} (URLs) are a specific form of
81 @dfn{Uniform Resource Identifiers} (URI) described in RFC 2396 which
82 updates RFC 1738 and RFC 1808. RFC 2016 defines uniform resource
85 URIs have the form @var{scheme}:@var{scheme-specific-part}, where the
86 @var{scheme}s supported by this library are described below.
87 @xref{Supported URL Types}.
89 FTP, NFS, HTTP, HTTPS, @code{rlogin}, @code{telnet}, tn3270,
90 IRC and gopher URLs all have the form
93 @var{scheme}://@r{[}@var{userinfo}@@@r{]}@var{hostname}@r{[}:@var{port}@r{]}@r{[}/@var{path}@r{]}
96 where @samp{@r{[}} and @samp{@r{]}} delimit optional parts.
97 @var{userinfo} sometimes takes the form @var{username}:@var{password}
98 but you should beware of the security risks of sending cleartext
99 passwords. @var{hostname} may be a domain name or a dotted decimal
100 address. If the @samp{:@var{port}} is omitted then the library will
101 use the `well known' port for that service when accessing URLs. With
102 the possible exception of @code{telnet}, it is rare for ports to be
103 specified, and it is possible using a non-standard port may have
104 undesired consequences if a different service is listening on that
105 port (e.g., an HTTP URL specifying the SMTP port can cause mail to be
106 sent). @c , but @xref{Other Variables, url-bad-port-list}.
107 The meaning of the @var{path} component depends on the service.
111 * Parsed URLs:: URLs are parsed into vector structures.
115 @section Configuration
117 @defvar url-configuration-directory
118 @cindex @file{~/.url}
119 @cindex configuration files
120 The directory in which URL configuration files, the cache etc.,
121 reside. Default @file{~/.url}.
127 The library functions typically operate on @dfn{parsed} versions of
128 URLs. These are actually vectors of the form:
131 [@var{type} @var{user} @var{password} @var{host} @var{port} @var{file} @var{target} @var{attributes} @var{full}]
137 is the type of the URL scheme, e.g., @code{http}
139 is the username associated with it, or @code{nil};
141 is the user password associated with it, or @code{nil};
143 is the host name associated with it, or @code{nil};
145 is the port number associated with it, or @code{nil};
147 is the `file' part of it, or @code{nil}. This doesn't necessarily
148 actually refer to a file;
150 is the target part, or @code{nil};
152 is the attributes associated with it, or @code{nil};
154 is @code{t} for a fully-specified URL, with a host part indicated by
155 @samp{//} after the scheme part.
165 @findex url-attributes
169 @findex url-set-password
173 @findex url-set-target
174 @findex url-set-attributes
176 These attributes have accessors named @code{url-@var{part}}, where
177 @var{part} is the name of one of the elements above, e.g.,
178 @code{url-host}. Similarly, there are setters of the form
179 @code{url-set-@var{part}}.
181 There are functions for parsing and unparsing between the string and
184 @defun url-generic-parse-url url
185 Return a parsed version of the string @var{url}.
188 @defun url-recreate-url url
189 @cindex unparsing URLs
190 Recreates a URL string from the parsed @var{url}.
193 @node Retrieving URLs
194 @chapter Retrieving URLs
196 @defun url-retrieve-synchronously url
197 Retrieve @var{url} synchronously and return a buffer containing the
198 data. @var{url} is either a string or a parsed URL structure. Return
199 @code{nil} if there are no data associated with it (the case for dired,
200 info, or mailto URLs that need no further processing).
203 @defun url-retrieve url callback &optional cbargs
204 Retrieve @var{url} asynchronously and call @var{callback} with args
205 @var{cbargs} when finished. The callback is called when the object
206 has been completely retrieved, with the current buffer containing the
207 object and any MIME headers associated with it. @var{url} is either a
208 string or a parsed URL structure. Returns the buffer @var{url} will
209 load into, or @code{nil} if the process has already completed.
212 @node Supported URL Types
213 @chapter Supported URL Types
216 * http/https:: Hypertext Transfer Protocol.
217 * file/ftp:: Local files and FTP archives.
218 * info:: Emacs `Info' pages.
219 * mailto:: Sending email.
220 * news/nntp/snews:: Usenet news.
221 * rlogin/telnet/tn3270:: Remote host connectivity.
222 * irc:: Internet Relay Chat.
223 * data:: Embedded data URLs.
224 * nfs:: Networked File System
231 * ldap:: Lightweight Directory Access Protocol
232 * imap:: IMAP mailboxes.
233 * man:: Unix man pages.
237 @section @code{http} and @code{https}
239 The scheme @code{http} is Hypertext Transfer Protocol. The library
240 supports version 1.1, specified in RFC 2616. (This supersedes 1.0,
241 defined in RFC 1945) HTTP URLs have the following form, where most of
242 the parts are optional:
244 http://@var{user}:@var{password}@@@var{host}:@var{port}/@var{path}?@var{searchpart}#@var{fragment}
246 @c The @code{:@var{port}} part is optional, and @var{port} defaults to
247 @c 80. The @code{/@var{path}} part, if present, is a slash-separated
248 @c series elements. The @code{?@var{searchpart}}, if present, is the
249 @c query for a search or the content of a form submission. The
250 @c @code{#fragment} part, if present, is a location in the document.
252 The scheme @code{https} is a secure version of @code{http}, with
253 transmission via SSL. It is defined in RFC 2069. Its default port is
254 443. This scheme depends on SSL support in Emacs via the
255 @file{ssl.el} library and is actually implemented by forcing the
256 @code{ssl} gateway method to be used. @xref{Gateways in general}.
258 @defopt url-honor-refresh-requests
259 This controls honoring of HTTP @samp{Refresh} headers by which
260 servers can direct clients to reload documents from the same URL or a
261 or different one. @code{nil} means they will not be honored,
262 @code{t} (the default) means they will always be honored, and
263 otherwise the user will be asked on each request.
269 * HTTP language/coding::
271 * Dealing with HTTP documents::
277 @defopt url-cookie-file
278 The file in which cookies are stored, defaulting to @file{cookies} in
279 the directory specified by @code{url-configuration-directory}.
282 @defopt url-cookie-confirmation
283 Specifies whether confirmation is require to accept cookies.
286 @defopt url-cookie-multiple-line
287 Specifies whether to put all cookies for the server on one line in the
288 HTTP request to satisfy broken servers like
289 @url{http://www.hotmail.com}.
292 @defopt url-cookie-trusted-urls
293 A list of regular expressions matching URLs from which to accept
297 @defopt url-cookie-untrusted-urls
298 A list of regular expressions matching URLs from which to reject
302 @defopt url-cookie-save-interval
303 The number of seconds between automatic saves of cookies to disk.
308 @node HTTP language/coding
309 @subsection Language and Encoding Preferences
311 HTTP allows clients to express preferences for the language and
312 encoding of documents which servers may honor. For each of these
313 variables, the value is a string; it can specify a single choice, or
314 it can be a comma-separated list.
316 Normally, this list is ordered by descending preference. However, each
317 element can be followed by @samp{;q=@var{priority}} to specify its
318 preference level, a decimal number from 0 to 1; e.g., for
319 @code{url-mime-language-string}, @w{@code{"de, en-gb;q=0.8,
320 en;q=0.7"}}. An element that has no @samp{;q} specification has
323 @defopt url-mime-charset-string
324 @cindex character sets
325 @cindex coding systems
326 This variable specifies a preference for character sets when documents
327 can be served in more than one encoding.
329 HTTP allows specifying a series of MIME charsets which indicate your
330 preferred character set encodings, e.g., Latin-9 or Big5, and these
331 can be weighted. The default series is generated automatically from
332 the associated MIME types of all defined coding systems, sorted by the
333 coding system priority specified in Emacs. @xref{Recognize Coding, ,
334 Recognizing Coding Systems, emacs, The GNU Emacs Manual}.
337 @defopt url-mime-language-string
338 @cindex language preferences
339 A string specifying the preferred language when servers can serve
340 files in several languages. Use RFC 1766 abbreviations, e.g.,
341 @samp{en} for English, @samp{de} for German.
343 The string can be @code{"*"} to get the first available language (as
344 opposed to the default).
347 @node HTTP URL Options
348 @subsection HTTP URL Options
350 HTTP supports an @samp{OPTIONS} method describing things supported by
353 @defun url-http-options url
354 Returns a property list describing options available for URL. The
355 property list members are:
359 A list of symbols specifying what HTTP methods the resource
364 A list of numbers specifying what DAV protocol/schema versions are
369 A list of supported DASL search types supported (string form).
372 A list of the units available for use in partial document fetches.
376 The @dfn{Platform For Privacy Protection} description for the resource.
377 Currently this is just the raw header contents.
382 @node Dealing with HTTP documents
383 @subsection Dealing with HTTP documents
385 HTTP URLs are retrieved into a buffer containing the HTTP headers
386 followed by the body. Since the headers are quasi-MIME, they may be
387 processed using the MIME library. @xref{Top,, Emacs MIME,
388 emacs-mime, The Emacs MIME Manual}. The URL package provides a
389 function to do this in general:
391 @defun url-decode-text-part handle &optional coding
392 This function decodes charset-encoded text in the current buffer. In
393 Emacs, the buffer is expected to be unibyte initially and is set to
394 multibyte after decoding.
395 HANDLE is the MIME handle of the original part. CODING is an explicit
396 coding to use, overriding what the MIME headers specify.
397 The coding system used for the decoding is returned.
399 Note that this function doesn't deal with @samp{http-equiv} charset
400 specifications in HTML @samp{<meta>} elements.
404 @section file and ftp
407 @cindex File Transfer Protocol
408 @cindex compressed files
412 ftp://@var{user}:@var{password}@@@var{host}:@var{port}/@var{file}
413 file://@var{user}:@var{password}@@@var{host}:@var{port}/@var{file}
416 These schemes are defined in RFC 1808.
417 @samp{ftp:} and @samp{file:} are synonymous in this library. They
418 allow reading arbitrary files from hosts. Either @samp{ange-ftp}
419 (Emacs) or @samp{efs} (XEmacs) is used to retrieve them from remote
420 hosts. Local files are accessed directly.
422 Compressed files are handled, but support is hard-coded so that
423 @code{jka-compr-compression-info-list} and so on have no affect.
424 Suffixes recognized are @samp{.z}, @samp{.gz}, @samp{.Z} and
427 @defopt url-directory-index-file
428 The filename to look for when indexing a directory, default
429 @samp{"index.html"}. If this file exists, and is readable, then it
430 will be viewed instead of using @code{dired} to view the directory.
437 @findex Info-goto-node
440 info:@var{file}#@var{node}
443 Info URLs are not officially defined. They invoke
444 @code{Info-goto-node} with argument @samp{(@var{file})@var{node}}.
445 @samp{#@var{node}} is optional, defaulting to @samp{Top}.
452 A mailto URL will send an email message to the address in the
453 URL, for example @samp{mailto:foo@@bar.com} would compose a
454 message to @samp{foo@@bar.com}.
456 @defopt url-mail-command
457 @vindex mail-user-agent
458 The function called whenever url needs to send mail. This should
459 normally be left to default from @var{mail-user-agent}. @xref{Mail
460 Methods, , Mail-Composition Methods, emacs, The GNU Emacs Manual}.
463 An @samp{X-Url-From} header field containing the URL of the document
464 that contained the mailto URL is added if that URL is known.
466 RFC 2368 extends the definition of mailto URLs in RFC 1738.
467 The form of a mailto URL is
469 @samp{mailto:@var{mailbox}[?@var{header}=@var{contents}[&@var{header}=@var{contents}]]}
471 @noindent where an arbitrary number of @var{header}s can be added. If the
472 @var{header} is @samp{body}, then @var{contents} is put in the body
473 otherwise a @var{header} header field is created with @var{contents}
474 as its contents. Note that the URL library does not consider any
475 headers `dangerous' so you should check them before sending the
479 Email messages are defined in @sc{rfc}822.
481 @node news/nntp/snews
482 @section @code{news}, @code{nntp} and @code{snews}
489 @c draft-gilman-news-url-01
490 The network news URL scheme take the following forms following RFC
491 1738 except that for compatibility with other clients, host and port
492 fields may be included in news URLs though they are properly only
493 allowed for nntp an snews.
496 @item news:@var{newsgroup}
497 Retrieves a list of messages in @var{newsgroup};
498 @item news:@var{message-id}
499 Retrieves the message with the given @var{message-id};
501 Retrieves a list of all available newsgroups;
502 @item nntp://@var{host}:@var{port}/@var{newsgroup}
503 @itemx nntp://@var{host}:@var{port}/@var{message-id}
504 @itemx nntp://@var{host}:@var{port}/*
505 Similar to the @samp{news} versions.
508 @samp{:@var{port}} is optional and defaults to :119.
510 @samp{snews} is the same as @samp{nntp} except that the default port
513 (It is tunneled through SSL.)
515 An @samp{nntp} URL is the same as a news URL, except that the URL may
516 specify an article by its number.
518 @defopt url-news-server
519 This variable can be used to override the default news server.
520 Usually this will be set by the Gnus package, which is used to fetch
522 @cindex environment variable
524 It may be set from the conventional environment variable
528 @node rlogin/telnet/tn3270
529 @section rlogin, telnet and tn3270
533 @cindex terminal emulation
534 @findex terminal-emulator
536 These URL schemes from RFC 1738 for logon via a terminal emulator have
539 telnet://@var{user}:@var{password}@@@var{host}:@var{port}
541 but the @code{:@var{password}} component is ignored.
543 To handle rlogin, telnet and tn3270 URLs, a @code{rlogin},
544 @code{telnet} or @code{tn3270} (the program names and arguments are
545 hardcoded) session is run in a @code{terminal-emulator} buffer.
546 Well-known ports are used if the URL does not specify a port.
551 @cindex Internet Relay Chat
555 @c Fixme: reference (was http://www.w3.org/Addressing/draft-mirashi-url-irc-01.txt)
556 @dfn{Internet Relay Chat} (IRC) is handled by handing off the @sc{irc}
557 session to a function named in @code{url-irc-function}.
559 @defopt url-irc-function
560 A function to actually open an IRC connection.
562 must take five arguments, @var{host}, @var{port}, @var{channel},
563 @var{user} and @var{password}. The @var{channel} argument specifies the
564 channel to join immediately, this can be @code{nil}. By default this is
565 @code{url-irc-rcirc}.
567 @defun url-irc-rcirc host port channel user password
568 Processes the arguments and lets @code{rcirc} handle the session.
570 @defun url-irc-erc host port channel user password
571 Processes the arguments and lets @code{ERC} handle the session.
573 @defun url-irc-zenirc host port channel user password
574 Processes the arguments and lets @code{zenirc} handle the session.
582 data:@r{[}@var{media-type}@r{]}@r{[};@var{base64}@r{]},@var{data}
585 Data URLs contain MIME data in the URL itself. They are defined in
588 @var{media-type} is a MIME @samp{Content-Type} string, possibly
589 including parameters. It defaults to
590 @samp{text/plain;charset=US-ASCII}. The @samp{text/plain} can be
591 omitted but the charset parameter supplied. If @samp{;base64} is
592 present, the @var{data} are base64-encoded.
597 @cindex Network File System
601 nfs://@var{user}:@var{password}@@@var{host}:@var{port}/@var{file}
604 The @samp{nfs:} scheme is defined in RFC 2224. It is similar to
605 @samp{ftp:} except that it points to a file on a remote host that is
606 handled by the automounter on the local host.
608 @defvar url-nfs-automounter-directory-spec
610 A string saying how to invoke the NFS automounter. Certain @samp{%}
611 sequences are recognized:
615 The hostname of the NFS server;
617 The port number of the NFS server;
619 The username to use to authenticate;
621 The password to use to authenticate;
623 The filename on the remote server;
628 Each can be used any number of times.
642 @cindex Lightweight Directory Access Protocol
644 The LDAP scheme is defined in RFC 2255.
654 @cindex @command{man}
655 @cindex Unix man pages
659 @samp{man:@var{page-spec}}
662 This is a non-standard scheme. @var{page-spec} is passed directly to
663 the Lisp @code{man} function.
665 @node Defining New URLs
666 @chapter Defining New URLs
669 * Naming conventions::
670 * Required functions::
671 * Optional functions::
672 * Asynchronous fetching::
673 * Supporting file-name-handlers::
676 @node Naming conventions
677 @section Naming conventions
679 @node Required functions
680 @section Required functions
682 @node Optional functions
683 @section Optional functions
685 @node Asynchronous fetching
686 @section Asynchronous fetching
688 @node Supporting file-name-handlers
689 @section Supporting file-name-handlers
691 @node General Facilities
692 @chapter General Facilities
697 * Gateways in general::
702 @section Disk Caching
704 @cindex Persistent Cache
707 The disk cache stores retrieved documents locally, whence they can be
708 retrieved more quickly. When requesting a URL that is in the cache,
709 the library checks to see if the page has changed since it was last
710 retrieved from the remote machine. If not, the local copy is used,
711 saving the transmission over the network.
712 @cindex Cleaning the cache
713 @cindex Clearing the cache
714 @cindex Cache cleaning
715 Currently the cache isn't cleared automatically.
716 @c Running the @code{clean-cache} shell script
717 @c fist is recommended, to allow for future cleaning of the cache. This
718 @c shell script will remove all files that have not been accessed since it
719 @c was last run. To keep the cache pared down, it is recommended that this
720 @c script be run from @i{at} or @i{cron} (see the manual pages for
721 @c crontab(5) or at(1) for more information)
723 @defopt url-automatic-caching
724 Setting this variable non-@code{nil} causes documents to be cached
728 @defopt url-cache-directory
729 This variable specifies the
730 directory to store the cache files. It defaults to sub-directory
731 @file{cache} of @code{url-configuration-directory}.
734 @defopt url-cache-creation-function
735 The cache relies on a scheme for mapping URLs to files in the cache.
736 This variable names a function which sets the type of cache to use.
737 It takes a URL as argument and returns the absolute file name of the
738 corresponding cache file. The two supplied possibilities are
739 @code{url-cache-create-filename-using-md5} and
740 @code{url-cache-create-filename-human-readable}.
743 @defun url-cache-create-filename-using-md5 url
744 Creates a cache file name from @var{url} using MD5 hashing.
745 This is creates entries with very few cache collisions and is fast.
748 (url-cache-create-filename-using-md5 "http://www.example.com/foo/bar")
749 @result{} "/home/fx/.url/cache/fx/http/com/example/www/b8a35774ad20db71c7c3409a5410e74f"
753 @defun url-cache-create-filename-human-readable url
754 Creates a cache file name from @var{url} more obviously connected to
755 @var{url} than for @code{url-cache-create-filename-using-md5}, but
756 more likely to conflict with other files.
758 (url-cache-create-filename-human-readable "http://www.example.com/foo/bar")
759 @result{} "/home/fx/.url/cache/fx/http/com/example/www/foo/bar"
763 @defun url-cache-expired
764 This function returns non-nil if a cache entry has expired (or is absent).
765 The arguments are a URL and optional expiration delay in seconds
766 (default @var{url-cache-expire-time}).
769 @defopt url-cache-expire-time
770 This variable is the default number of seconds to use for the
771 expire-time argument of the function @code{url-cache-expired}.
774 @defun url-fetch-from-cache
775 This function takes a URL as its argument and returns a buffer
776 containing the data cached for that URL.
779 @c Fixme: never actually used currently?
780 @c @defopt url-standalone-mode
781 @c @cindex Relying on cache
782 @c @cindex Cache only mode
783 @c @cindex Standalone mode
784 @c If this variable is non-@code{nil}, the library relies solely on the
785 @c cache for fetching documents and avoids checking if they have changed
786 @c on remote servers.
789 @c With a large cache of documents on the local disk, it can be very handy
790 @c when traveling, or any other time the network connection is not active
791 @c (a laptop with a dial-on-demand PPP connection, etc). Emacs/W3 can rely
792 @c solely on its cache, and avoid checking to see if the page has changed
793 @c on the remote server. In the case of a dial-on-demand PPP connection,
794 @c this will keep the phone line free as long as possible, only bringing up
795 @c the PPP connection when asking for a page that is not located in the
796 @c cache. This is very useful for demonstrations as well.
799 @section Proxies and Gatewaying
801 @c fixme: check/document url-ns stuff
802 @cindex proxy servers
804 @cindex environment variables
806 Proxy servers are commonly used to provide gateways through firewalls
807 or as caches serving some more-or-less local network. Each protocol
808 (HTTP, FTP, etc.)@: can have a different gateway server. Proxying is
809 conventionally configured commonly amongst different programs through
810 environment variables of the form @code{@var{protocol}_proxy}, where
811 @var{protocol} is one of the supported network protocols (@code{http},
812 @code{ftp} etc.). The library recognizes such variables in either
813 upper or lower case. Their values are of one of the forms:
815 @item @code{@var{host}:@var{port}}
817 @item Simply a host name.
821 The @code{NO_PROXY} environment variable specifies URLs that should be
822 excluded from proxying (on servers that should be contacted directly).
823 This should be a comma-separated list of hostnames, domain names, or a
824 mixture of both. Asterisks can be used as wildcards, but other
825 clients may not support that. Domain names may be indicated by a
826 leading dot. For example:
828 NO_PROXY="*.aventail.com,home.com,.seanet.com"
830 @noindent says to contact all machines in the @samp{aventail.com} and
831 @samp{seanet.com} domains directly, as well as the machine named
832 @samp{home.com}. If @code{NO_PROXY} isn't defined, @code{no_PROXY}
833 and @code{no_proxy} are also tried, in that order.
835 Proxies may also be specified directly in Lisp.
837 @defopt url-proxy-services
838 This variable is an alist of URL schemes and proxy servers that
839 gateway them. The items are of the form @w{@code{(@var{scheme}
840 . @var{host}:@var{portnumber})}}, says that the URL @var{scheme} is
841 gatewayed through @var{portnumber} on the specified @var{host}. An
842 exception is the pseudo scheme @code{"no_proxy"}, which is paired with
843 a regexp matching host names not to be proxied. This variable is
844 initialized from the environment as above.
847 (setq url-proxy-services
848 '(("http" . "proxy.aventail.com:80")
849 ("no_proxy" . "^.*\\(aventail\\|seanet\\)\\.com")))
853 @node Gateways in general
854 @section Gateways in General
858 The library provides a general gateway layer through which all
859 networking passes. It can both control access to the network and
860 provide access through gateways in firewalls. This may make direct
861 connections in some cases and pass through some sort of gateway in
862 others.@footnote{Proxies (which only operate over HTTP) are
863 implemented using this.} The library's basic function responsible for
864 making connections is @code{url-open-stream}.
866 @defun url-open-stream name buffer host service
867 @cindex opening a stream
868 @cindex stream, opening
869 Open a stream to @var{host}, possibly via a gateway. The other
870 arguments are as for @code{open-network-stream}. This will not make a
871 connection if @code{url-gateway-unplugged} is non-@code{nil}.
874 @defvar url-gateway-local-host-regexp
875 This is a regular expression that matches local hosts that do not
876 require the use of a gateway. If @code{nil}, all connections are made
880 @defvar url-gateway-method
881 This variable controls which gateway method is used. It may be useful
882 to bind it temporarily in some applications. It has values taken from
883 a list of symbols. Possible values are:
887 @cindex @command{telnet}
888 Use this method if you must first telnet and log into a gateway host,
889 and then run telnet from that host to connect to outside machines.
892 @cindex @command{rlogin}
893 This method is identical to @code{telnet}, but uses @command{rlogin}
894 to log into the remote machine without having to send the username and
895 password over the wire every time.
899 Use if the firewall has a @sc{socks} gateway running on it. The
900 @sc{socks} v5 protocol is defined in RFC 1928.
903 @c This probably shouldn't be documented
904 @c Fixme: why not? -- fx
907 This method uses Emacs's builtin networking directly. This is the
908 default. It can be used only if there is no firewall blocking access.
912 The following variables control the gateway methods.
914 @defopt url-gateway-telnet-host
915 The gateway host to telnet to. Once logged in there, you then telnet
916 out to the hosts you want to connect to.
918 @defopt url-gateway-telnet-parameters
919 This should be a list of parameters to pass to the @command{telnet} program.
921 @defopt url-gateway-telnet-password-prompt
922 This is a regular expression that matches the password prompt when
925 @defopt url-gateway-telnet-login-prompt
926 This is a regular expression that matches the username prompt when
929 @defopt url-gateway-telnet-user-name
930 The username to log in with.
932 @defopt url-gateway-telnet-password
933 The password to send when logging in.
935 @defopt url-gateway-prompt-pattern
936 This is a regular expression that matches the shell prompt.
939 @defopt url-gateway-rlogin-host
940 Host to @samp{rlogin} to before telnetting out.
942 @defopt url-gateway-rlogin-parameters
943 Parameters to pass to @samp{rsh}.
945 @defopt url-gateway-rlogin-user-name
946 User name to use when logging in to the gateway.
948 @defopt url-gateway-prompt-pattern
949 This is a regular expression that matches the shell prompt.
953 This specifies the default server, it takes the form
954 @w{@code{("Default server" @var{server} @var{port} @var{version})}}
955 where @var{version} can be either 4 or 5.
957 @defvar socks-password
958 If this is @code{nil} then you will be asked for the password,
959 otherwise it will be used as the password for authenticating you to
960 the @sc{socks} server.
962 @defvar socks-username
963 This is the username to use when authenticating yourself to the
964 @sc{socks} server. By default this is your login name.
966 @defvar socks-timeout
967 This controls how long, in seconds, to wait for responses from the
968 @sc{socks} server; it is 5 by default.
970 @c fixme: these have been effectively commented-out in the code
971 @c @defopt socks-server-aliases
972 @c This a list of server aliases. It is a list of aliases of the form
973 @c @var{(alias hostname port version)}.
975 @c @defopt socks-network-aliases
976 @c This a list of network aliases. Each entry in the list takes the form
977 @c @var{(alias (network))} where @var{alias} is a string that names the
978 @c @var{network}. The networks can contain a pair (not a dotted pair) of
979 @c @sc{ip} addresses which specify a range of @sc{ip} addresses, an @sc{ip}
980 @c address and a netmask, a domain name or a unique hostname or @sc{ip}
983 @c @defopt socks-redirection-rules
984 @c This a list of redirection rules. Each rule take the form
985 @c @var{(Destination network Connection type)} where @var{Destination
986 @c network} is a network alias from @code{socks-network-aliases} and
987 @c @var{Connection type} can be @code{nil} in which case a direct
988 @c connection is used, or it can be an alias from
989 @c @code{socks-server-aliases} in which case that server is used as a
992 @defopt socks-nslookup-program
993 @cindex @command{nslookup}
994 This the @samp{nslookup} program. It is @code{"nslookup"} by default.
998 * Suppressing network connections::
1000 @c * Broken hostname resolution::
1002 @node Suppressing network connections
1003 @subsection Suppressing Network Connections
1005 @cindex network connections, suppressing
1006 @cindex suppressing network connections
1009 In some circumstances it is desirable to suppress making network
1010 connections. A typical case is when rendering HTML in a mail user
1011 agent, when external URLs should not be activated, particularly to
1012 avoid `bugs' which `call home' by fetch single-pixel images and the
1013 like. To arrange this, bind the following variable for the duration
1016 @defvar url-gateway-unplugged
1017 If this variable is non-@code{nil} new network connections are never
1018 opened by the URL library.
1021 @c @node Broken hostname resolution
1022 @c @subsection Broken Hostname Resolution
1024 @c @cindex hostname resolver
1025 @c @cindex resolver, hostname
1026 @c Some C libraries do not include the hostname resolver routines in
1027 @c their static libraries. If Emacs was linked statically, and was not
1028 @c linked with the resolver libraries, it will not be able to get to any
1029 @c machines off the local network. This is characterized by being able
1030 @c to reach someplace with a raw ip number, but not its hostname
1031 @c (@url{http://129.79.254.191/} works, but
1032 @c @url{http://www.cs.indiana.edu/} doesn't). This used to happen on
1033 @c SunOS4 and Ultrix, but is now probably now rare. If Emacs can't be
1034 @c rebuilt linked against the resolver library, it can use the external
1035 @c @command{nslookup} program instead.
1037 @c @defopt url-gateway-broken-resolution
1038 @c @cindex @code{nslookup} program
1039 @c @cindex program, @code{nslookup}
1040 @c If non-@code{nil}, this variable says to use the program specified by
1041 @c @code{url-gateway-nslookup-program} program to do hostname resolution.
1044 @c @defopt url-gateway-nslookup-program
1045 @c The name of the program to do hostname lookup if Emacs can't do it
1046 @c directly. This program should expect a single argument on the command
1047 @c line---the hostname to resolve---and should produce output similar to
1048 @c the standard Unix @command{nslookup} program:
1050 @c Name: www.cs.indiana.edu
1051 @c Address: 129.79.254.191
1058 @findex url-do-setup
1059 The library can maintain a global history list tracking URLs accessed.
1060 URL completion can be done from it. The history mechanism is set up
1061 automatically via @code{url-do-setup} when it is configured to be on.
1062 Note that the size of the history list is currently not limited.
1064 @vindex url-history-hash-table
1065 The history `list' is actually a hash table,
1066 @code{url-history-hash-table}. It contains access times keyed by URL
1067 strings. The times are in the format returned by @code{current-time}.
1069 @defun url-history-update-url url time
1070 This function updates the history table with an entry for @var{url}
1071 accessed at the given @var{time}.
1074 @defopt url-history-track
1075 If non-@code{nil}, the library will keep track of all the URLs
1076 accessed. If it is @code{t}, the list is saved to disk at the end of
1077 each Emacs session. The default is @code{nil}.
1080 @defopt url-history-file
1081 The file storing the history list between sessions. It defaults to
1082 @file{history} in @code{url-configuration-directory}.
1085 @defopt url-history-save-interval
1086 @findex url-history-setup-save-timer
1087 The number of seconds between automatic saves of the history list.
1088 Default is one hour. Note that if you change this variable directly,
1089 rather than using Custom, after @code{url-do-setup} has been run, you
1090 need to run the function @code{url-history-setup-save-timer}.
1093 @defun url-history-parse-history &optional fname
1094 Parses the history file @var{fname} (default @code{url-history-file})
1095 and sets up the history list.
1098 @defun url-history-save-history &optional fname
1099 Saves the current history to file @var{fname} (default
1100 @code{url-history-file}).
1103 @defun url-completion-function string predicate function
1104 You can use this function to do completion of URLs from the history.
1108 @chapter Customization
1110 @section Environment Variables
1112 @cindex environment variables
1113 The following environment variables affect the library's operation at
1119 @vindex url-temporary-directory
1120 If this is defined, @var{url-temporary-directory} is initialized from
1124 @section General User Options
1126 The following user options, settable with Customize, affect the
1127 general operation of the package.
1131 Specifies the types of debug messages which are logged to
1132 the @code{*URL-DEBUG*} buffer.
1133 @code{t} means log all messages.
1134 A number means log all messages and show them with @code{message}.
1135 It may also be a list of the types of messages to be logged.
1137 @defopt url-personal-mail-address
1139 @defopt url-privacy-level
1141 @defopt url-uncompressor-alist
1143 @defopt url-passwd-entry-func
1145 @defopt url-standalone-mode
1147 @defopt url-bad-port-list
1149 @defopt url-max-password-attempts
1151 @defopt url-temporary-directory
1153 @defopt url-show-status
1155 @defopt url-confirmation-func
1156 The function to use for asking yes or no functions. This is normally
1157 either @code{y-or-n-p} or @code{yes-or-no-p}, but could be another
1158 function taking a single argument (the prompt) and returning @code{t}
1159 only if an affirmative answer is given.
1161 @defopt url-gateway-method
1162 @c fixme: describe gatewaying
1163 A symbol specifying the type of gateway support to use for connections
1164 from the local machine. The supported methods are:
1168 Run telnet in a subprocess to connect;
1170 Rlogin to another machine to connect;
1172 Connect through a socks server;
1180 @node GNU Free Documentation License
1181 @appendix GNU Free Documentation License
1182 @include doclicense.texi
1184 @node Function Index
1185 @unnumbered Command and Function Index
1188 @node Variable Index
1189 @unnumbered Variable Index
1193 @unnumbered Concept Index
1199 arch-tag: c96be356-7e2d-4196-bcda-b13246c5c3f0