| blob | 53798f77c399960a02f157bf40aa836677faa636 |
1 ;;; url-http.el --- HTTP retrieval routines -*- lexical-binding:t -*-
3 ;; Copyright (C) 1999, 2001, 2004-2018 Free Software Foundation, Inc.
5 ;; Author: Bill Perry <wmperry@gnu.org>
6 ;; Maintainer: emacs-devel@gnu.org
7 ;; Keywords: comm, data, processes
9 ;; This file is part of GNU Emacs.
10 ;;
11 ;; GNU Emacs is free software: you can redistribute it and/or modify
12 ;; it under the terms of the GNU General Public License as published by
13 ;; the Free Software Foundation, either version 3 of the License, or
14 ;; (at your option) any later version.
16 ;; GNU Emacs is distributed in the hope that it will be useful,
17 ;; but WITHOUT ANY WARRANTY; without even the implied warranty of
18 ;; MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
19 ;; GNU General Public License for more details.
21 ;; You should have received a copy of the GNU General Public License
22 ;; along with GNU Emacs. If not, see <https://www.gnu.org/licenses/>.
24 ;;; Commentary:
26 ;;; Code:
79 "What version of HTTP we advertise, as a string.
80 Valid values are 1.1 and 1.0.
81 This is only useful when debugging the HTTP subsystem.
83 Setting this to 1.0 will tell servers not to send chunked encoding,
87 "Whether to use a single TCP connection multiple times in HTTP.
88 This is only useful when debugging the HTTP subsystem. Setting to
89 nil will explicitly close the connection to the server after every
144 ;(eval-when-compile
145 ;; These are all macros so that they are hidden from external sight
146 ;; when the file is byte-compiled.
147 ;;
148 ;; This allows us to expose just the entry points we want.
150 ;; These routines will allow us to implement persistent HTTP
151 ;; connections.
155 ;; The user hit C-g, honor it! Some things can get in an
156 ;; incredibly tight loop (chunked encoding)
169 url-http-open-connections)
170 proc)
180 url-http-open-connections))
181 nil)
202 ;; `url-open-stream' needs a buffer in which to do things
203 ;; like authentication. But we use another buffer afterwards.
208 host)
211 port)
212 gateway-method)))
213 ;; url-open-stream might return nil.
215 ;; Drop the temp buffer link before killing the buffer.
218 ;; If there was an error on connect, make sure we don't
219 ;; get queried.
228 "Compute a default User-Agent string based on `url-privacy-level'."
239 emacs-info os-info))
243 (url-http-debug "getting referer from buffer: buffer:%S target-url:%S lastloc:%S" (current-buffer) url url-current-lastloc)
253 ;; url-privacy-level allows referer. But url-lastloc-privacy-level
254 ;; may restrict who we send it to.
260 referer-string)))
265 url-domain
267 referer-string)))
269 referer-string)))))))
271 ;; Building an HTTP request
273 "Compute a User-Agent string.
274 The string is based on `url-privacy-level' and `url-user-agent'."
288 "Create an HTTP request for `url-http-target-url', using `url-http-referer'
289 as the Referer-header (subject to `url-privacy-level'."
295 url-http-extra-headers))
297 nil
304 nil
307 proxy-info)
318 ;; Protection against stupid values in the referrer
323 ;; url-http-extra-headers contains an assoc-list of
324 ;; header/value pairs that we need to put into the request.
332 ;; This was done with a call to `format'. Concatenating parts has
333 ;; the advantage of keeping the parts of each header together and
334 ;; allows us to elide null lines directly, at the cost of making
335 ;; the layout less clear.
338 ;; The request
343 ;; Version of MIME we speak
345 ;; (maybe) Try to keep the connection open
349 ;; HTTP extensions we support
353 ;; Who we want to talk to
363 ;; Who its from
367 ;; Encodings we understand
369 ;; MS-Windows loads zlib dynamically, so recheck
370 ;; in case they made it available since
371 ;; initialization in url-vars.el.
380 "Accept-charset: "
383 ;; Languages we understand
387 ;; Types we understand
389 ;; User agent
391 ;; Proxy Authorization
392 proxy-auth
393 ;; Authorization
394 auth
395 ;; Cookies
399 host real-fname
401 ;; If-modified-since
408 ;; Whence we came
411 extra-headers
412 ;; Length of data
418 ;; End request
420 ;; Any data
421 url-http-data))
422 ;; Bug#23750
427 request))
432 s))
434 ;; Parsing routines
437 This allows us to use `mail-fetch-field', etc.
438 Return the number of characters removed."
450 nil nil t))
456 url-http-proxy
457 url-current-object)))
459 ;; Cheating, but who cares? :)
460 'url-http-proxy-basic-auth-storage
462 auth
465 ;; find strongest supported auth
469 this-auth)))
473 this-auth)))
478 type this-type
479 strength this-strength))))
486 " authentication. If you'd like to write it,"
488 ;; We used to set a `status' var (declared "special") but I can't
489 ;; find the corresponding let-binding, so it's probably an error.
490 ;; FIXME: Maybe it was supposed to set `success', i.e. to return t?
491 ;; (setq status t)
497 type t args)))
499 t ;Success.
501 url-http-extra-headers)
506 url-callback-arguments))
510 "Parse just the response code."
525 "Handle all set-cookie / set-cookie2 headers in an HTTP response.
526 The buffer must already be narrowed to the headers, so `mail-fetch-field' will
527 work correctly."
534 ;;; (while cookies2
535 ;;; (url-cookie-handle-set-cookie2 (pop cookies)))
536 )
537 )
543 "Parse and handle HTTP specific headers.
544 Return t if and only if the current buffer is still active and
545 should be shown to the user."
546 ;; The comments after each status code handled are taken from RFC
547 ;; 2616 (HTTP/1.1)
550 url-http-process)
551 ;; Pass the https certificate on to the caller.
566 ;;(narrow-to-region (point-min) url-http-end-of-headers)
568 ;; In HTTP 1.0, keep the connection only if there is a
569 ;; "Connection: keep-alive" header.
570 ;; In HTTP 1.1 (and greater), keep the connection unless there is a
571 ;; "Connection: close" header
584 ;; other status symbols: jewelry and luxury cars
587 class url-http-response-status)
592 ;; Classes of response codes
593 ;;
594 ;; 5xx = Server Error
595 ;; 4xx = Client Error
596 ;; 3xx = Redirection
597 ;; 2xx = Successful
598 ;; 1xx = Informational
600 ;; 100 = Continue with request
601 ;; 101 = Switching protocols
602 ;; 102 = Processing (Added by DAV)
605 url-http-response-status))
607 ;; 200 Ok
608 ;; 201 Created
609 ;; 202 Accepted
610 ;; 203 Non-authoritative information
611 ;; 204 No content
612 ;; 205 Reset content
613 ;; 206 Partial content
614 ;; 207 Multi-status (Added by DAV)
617 ;; No new data, just stay at the same document
620 ;; Generic success for all others. Store in the cache, and
621 ;; mark it as successful.
627 ;; 300 Multiple choices
628 ;; 301 Moved permanently
629 ;; 302 Found
630 ;; 303 See other
631 ;; 304 Not modified
632 ;; 305 Use proxy
633 ;; 307 Temporary redirect
638 ;; Quoth the spec (section 10.3.1)
639 ;; -------------------------------
640 ;; The requested resource corresponds to any one of a set of
641 ;; representations, each with its own specific location and
642 ;; agent-driven negotiation information is being provided so
643 ;; that the user can select a preferred representation and
644 ;; redirect its request to that location.
645 ;; [...]
646 ;; If the server has a preferred choice of representation, it
647 ;; SHOULD include the specific URI for that representation in
648 ;; the Location field; user agents MAY use the Location field
649 ;; value for automatic redirection.
650 ;; -------------------------------
651 ;; We do not support agent-driven negotiation, so we just
652 ;; redirect to the preferred URI if one is provided.
653 nil)
655 ;; 302 Found was ambiguously defined in the standards, but
656 ;; it's now recommended that it's treated like 303 instead
657 ;; of 307, since that's what most servers expect.
659 url-http-data nil))
661 ;; The response to the request can be found under a different
662 ;; URI and SHOULD be retrieved using a GET method on that
663 ;; resource.
665 url-http-data nil))
667 ;; The 304 response MUST NOT contain a message-body.
672 success t))
674 ;; The requested resource MUST be accessed through the
675 ;; proxy given by the Location field. The Location field
676 ;; gives the URI of the proxy. The recipient is expected
677 ;; to repeat this single request via the proxy. 305
678 ;; responses MUST only be generated by origin servers.
680 redirect-uri))
682 ;; Treat everything like '300'
683 nil))
685 ;; Clean off any whitespace and/or <...> cruft.
691 ;; Some stupid sites (like sourceforge) send a
692 ;; non-fully-qualified URL (ie: /), which royally confuses
693 ;; the URL library.
695 ;; Be careful to use the real target URL, otherwise we may
696 ;; compute the redirection relative to the URL of the proxy.
699 ;; Do not automatically include an authorization header in the
700 ;; redirect. If needed it will be regenerated by the relevant
701 ;; auth scheme when the new request happens.
708 ;; Check existing number of redirects
719 ;; url-max-redirections hasn't been reached, so go
720 ;; ahead and redirect.
722 ;; Remember that the request was redirected.
726 ;; Put in the current buffer a forwarding pointer to the new
727 ;; destination buffer.
728 ;; FIXME: This is a hack to fix url-retrieve-synchronously
729 ;; without changing the API. Instead url-retrieve should
730 ;; either simply not return the "destination" buffer, or it
731 ;; should take an optional `dest-buf' argument.
734 redirect-uri url-callback-function
735 url-callback-arguments
739 ;; We hit url-max-redirections, so issue an error and
740 ;; stop redirecting.
744 redirect-uri))
748 ;; 400 Bad Request
749 ;; 401 Unauthorized
750 ;; 402 Payment required
751 ;; 403 Forbidden
752 ;; 404 Not found
753 ;; 405 Method not allowed
754 ;; 406 Not acceptable
755 ;; 407 Proxy authentication required
756 ;; 408 Request time-out
757 ;; 409 Conflict
758 ;; 410 Gone
759 ;; 411 Length required
760 ;; 412 Precondition failed
761 ;; 413 Request entity too large
762 ;; 414 Request-URI too large
763 ;; 415 Unsupported media type
764 ;; 416 Requested range not satisfiable
765 ;; 417 Expectation failed
766 ;; 422 Unprocessable Entity (Added by DAV)
767 ;; 423 Locked
768 ;; 424 Failed Dependency
772 ;; The request requires user authentication. The response
773 ;; MUST include a WWW-Authenticate header field containing a
774 ;; challenge applicable to the requested resource. The
775 ;; client MAY repeat the request with a suitable
776 ;; Authorization header field.
779 ;; This code is reserved for future use
783 ;; The server understood the request, but is refusing to
784 ;; fulfill it. Authorization will not help and the request
785 ;; SHOULD NOT be repeated.
786 t)
788 ;; Not found
789 t)
791 ;; The method specified in the Request-Line is not allowed
792 ;; for the resource identified by the Request-URI. The
793 ;; response MUST include an Allow header containing a list of
794 ;; valid methods for the requested resource.
795 t)
797 ;; The resource identified by the request is only capable of
798 ;; generating response entities which have content
799 ;; characteristics not acceptable according to the accept
800 ;; headers sent in the request.
801 t)
803 ;; This code is similar to 401 (Unauthorized), but indicates
804 ;; that the client must first authenticate itself with the
805 ;; proxy. The proxy MUST return a Proxy-Authenticate header
806 ;; field containing a challenge applicable to the proxy for
807 ;; the requested resource.
810 ;; The client did not produce a request within the time that
811 ;; the server was prepared to wait. The client MAY repeat
812 ;; the request without modifications at any later time.
813 t)
815 ;; The request could not be completed due to a conflict with
816 ;; the current state of the resource. This code is only
817 ;; allowed in situations where it is expected that the user
818 ;; might be able to resolve the conflict and resubmit the
819 ;; request. The response body SHOULD include enough
820 ;; information for the user to recognize the source of the
821 ;; conflict.
822 t)
824 ;; The requested resource is no longer available at the
825 ;; server and no forwarding address is known.
826 t)
828 ;; The server refuses to accept the request without a defined
829 ;; Content-Length. The client MAY repeat the request if it
830 ;; adds a valid Content-Length header field containing the
831 ;; length of the message-body in the request message.
832 ;;
833 ;; NOTE - this will never happen because
834 ;; `url-http-create-request' automatically calculates the
835 ;; content-length.
836 t)
838 ;; The precondition given in one or more of the
839 ;; request-header fields evaluated to false when it was
840 ;; tested on the server.
841 t)
843 ;; The server is refusing to process a request because the
844 ;; request entity|URI is larger than the server is willing or
845 ;; able to process.
846 t)
848 ;; The server is refusing to service the request because the
849 ;; entity of the request is in a format not supported by the
850 ;; requested resource for the requested method.
851 t)
853 ;; A server SHOULD return a response with this status code if
854 ;; a request included a Range request-header field, and none
855 ;; of the range-specifier values in this field overlap the
856 ;; current extent of the selected resource, and the request
857 ;; did not include an If-Range request-header field.
858 t)
860 ;; The expectation given in an Expect request-header field
861 ;; could not be met by this server, or, if the server is a
862 ;; proxy, the server has unambiguous evidence that the
863 ;; request could not be met by the next-hop server.
864 t)
866 ;; The request could not be understood by the server due to
867 ;; malformed syntax. The client SHOULD NOT repeat the
868 ;; request without modifications.
869 t)))
870 ;; Tell the callback that an error occurred, and what the
871 ;; status code was.
877 ;; 500 Internal server error
878 ;; 501 Not implemented
879 ;; 502 Bad gateway
880 ;; 503 Service unavailable
881 ;; 504 Gateway time-out
882 ;; 505 HTTP version not supported
883 ;; 507 Insufficient storage
887 ;; The server does not support the functionality required to
888 ;; fulfill the request.
889 nil)
891 ;; The server, while acting as a gateway or proxy, received
892 ;; an invalid response from the upstream server it accessed
893 ;; in attempting to fulfill the request.
894 nil)
896 ;; The server is currently unable to handle the request due
897 ;; to a temporary overloading or maintenance of the server.
898 ;; The implication is that this is a temporary condition
899 ;; which will be alleviated after some delay. If known, the
900 ;; length of the delay MAY be indicated in a Retry-After
901 ;; header. If no Retry-After is given, the client SHOULD
902 ;; handle the response as it would for a 500 response.
903 nil)
905 ;; The server, while acting as a gateway or proxy, did not
906 ;; receive a timely response from the upstream server
907 ;; specified by the URI (e.g. HTTP, FTP, LDAP) or some other
908 ;; auxiliary server (e.g. DNS) it needed to access in
909 ;; attempting to complete the request.
910 nil)
912 ;; The server does not support, or refuses to support, the
913 ;; HTTP protocol version that was used in the request
914 ;; message.
915 nil)
917 ;; The method could not be performed on the resource
918 ;; because the server is unable to store the representation
919 ;; needed to successfully complete the request. This
920 ;; condition is considered to be temporary. If the request
921 ;; which received this status code was the result of a user
922 ;; action, the request MUST NOT be repeated until it is
923 ;; requested by a separate user action.
924 nil))
925 ;; Tell the callback that an error occurred, and what the
926 ;; status code was.
933 class url-http-response-status)))
940 success))
956 ;; Miscellaneous
958 "Activate callback specified when this buffer was created."
961 url-http-process)
966 ;; )
968 ;; These unfortunately cannot be macros... please ignore them!
970 "Remove (now defunct) process PROC from the list of open connections."
974 url-http-open-connections))
977 ;; Sentinel used to handle (i) terminated old HTTP/0.9 connections,
978 ;; and (ii) closed connection due to reusing a HTTP connection which
979 ;; we believed was still alive, but which the server closed on us.
980 ;; We handle case (ii) by calling `url-http' again.
989 ;; HTTP/0.9 just gets passed back no matter what
991 ;; Call `url-http' again if our connection expired.
997 url-current-object
1008 ;; Function used when we do NOT know how long the document is going to be
1009 ;; Just _very_ simple 'downloaded %d' type of info.
1013 "Function used when we DO know how long the document is going to be.
1014 More sophisticated percentage downloaded, etc.
1015 Also does minimal parsing of HTTP headers and will actually cause
1016 the callback to be triggered."
1019 "Reading [%s]... %s of %s (%d%%)"
1021 url-http-content-length)
1022 url-http-content-type
1026 url-http-content-length))
1028 "Reading... %s of %s (%d%%)"
1030 url-http-content-length)
1034 url-http-content-length)))
1038 ;; Found the end of the document! Wheee!
1045 "Function used when dealing with chunked encoding.
1046 Cannot give a sophisticated percentage, but we need a different
1047 function to look for the special 0-length chunk that signifies
1048 the end of the document."
1055 ;; We need to loop thru looking for more chunks even within
1056 ;; one after-change-function call.
1061 "Reading [%s]... chunk #%d"
1062 url-http-content-type url-http-chunked-counter)
1064 "Reading... chunk #%d"
1065 url-http-chunked-counter))
1067 url-http-chunked-counter st nd length)
1073 ;; We know how long the chunk is supposed to be, skip over
1074 ;; leading crap if possible.
1078 url-http-chunked-counter)
1080 url-http-chunked-length)))
1083 url-http-chunked-length)
1084 nd))
1091 ;; Must not have received the entirety of the chunk header,
1092 ;; need to spin some more.
1097 'end-open t
1098 'chunked-encoding t
1110 ; (if (not url-http-debug)
1113 url-http-chunked-counter url-http-chunked-length
1117 ;; Found the end of the document! Wheee!
1121 ;; Every chunk, even the last 0-length one, is
1122 ;; terminated by CRLF. Skip it.
1132 ;; This will wait for the headers to arrive and then splice in the
1133 ;; next appropriate after-change-function, etc.
1139 ;; (content-length nil)
1140 )
1145 ;; Not HTTP/x.y data, must be 0.9
1146 ;; God, I wish this could die.
1148 url-http-end-of-headers 0
1149 old-http t)
1150 ;; Blank line at end of headers.
1153 ;; Saw the end of the headers
1157 end-of-headers t)
1161 ;; Haven't seen the end of the headers yet, need to wait
1162 ;; for more data to arrive.
1163 nil
1180 ;; We got back a headerless malformed response from the
1181 ;; server.
1190 ;; A HEAD request is _ALWAYS_ terminated by the header
1191 ;; information, regardless of any entity headers,
1192 ;; according to section 4.4 of the HTTP/1.1 draft.
1198 ;; A CONNECT request is finished, but we cannot stick this
1199 ;; back on the free connection list
1204 ;; Only allowed to have a header section. We have to handle
1205 ;; this here instead of in url-http-parse-headers because if
1206 ;; you have a cached copy of something without a known
1207 ;; content-length, and try to retrieve it from the cache, we'd
1208 ;; fall into the 'being dumb' section and wait for the
1209 ;; connection to terminate, which means we'd wait for 10
1210 ;; seconds for the keep-alives to time out on some servers.
1214 ;; HTTP/0.9 always signaled end-of-connection by closing the
1215 ;; connection.
1237 ;; We got a NULL body! Activate the callback
1238 ;; immediately!
1244 ;; Have some leftover data
1248 nd
1251 nil)))
1256 ;; We are still at the beginning of the buffer... must just be
1257 ;; waiting for a response.
1263 "Retrieve URL via HTTP asynchronously.
1264 URL must be a parsed URL. See `url-generic-parse-url' for details.
1266 When retrieval is completed, execute the function CALLBACK,
1267 passing it an updated value of CBARGS as arguments. The first
1268 element in CBARGS should be a plist describing what has happened
1269 so far during the request, as described in the docstring of
1270 `url-retrieve' (if in doubt, specify nil). The current buffer
1271 then CALLBACK is executed is the retrieval buffer.
1273 Optional arg RETRY-BUFFER, if non-nil, specifies the buffer of a
1274 previous `url-http' call, which is being re-attempted.
1276 Optional arg GATEWAY-METHOD specifies the gateway to be used,
1277 overriding the value of `url-gateway-method'.
1279 The return value of this function is the retrieval buffer."
1282 ;; (port (url-port (or url-using-proxy url)))
1285 url-http-noninteractive)))
1286 ;; The following binding is needed in url-open-stream, which
1287 ;; is called from url-http-find-free-connection.
1291 gateway-method))
1298 ;; Failed to open the connection for some reason
1310 url-http-content-type
1311 url-http-content-length
1312 url-http-transfer-encoding
1313 url-http-after-change-function
1314 url-http-response-version
1315 url-http-response-status
1316 url-http-chunked-length
1317 url-http-chunked-counter
1318 url-http-chunked-start
1319 url-callback-function
1320 url-callback-arguments
1321 url-show-status
1322 url-http-process
1323 url-http-method
1324 url-http-extra-headers
1325 url-http-noninteractive
1326 url-http-data
1327 url-http-target-url
1328 url-http-no-retry
1329 url-http-connection-opened
1330 url-mime-accept-string
1331 url-http-proxy
1332 url-http-referer))
1336 url-http-extra-headers url-request-extra-headers
1337 url-http-noninteractive url-request-noninteractive
1338 url-http-data url-request-data
1339 url-http-process connection
1340 url-http-chunked-length nil
1341 url-http-chunked-start nil
1342 url-http-chunked-counter 0
1343 url-callback-function callback
1344 url-callback-arguments cbargs
1345 url-http-after-change-function 'url-http-wait-for-headers-change-function
1346 url-http-target-url url-current-object
1347 url-http-no-retry retry-buffer
1348 url-http-connection-opened nil
1349 url-mime-accept-string mime-accept-string
1350 url-http-proxy url-using-proxy
1351 url-http-referer referer)
1356 (`connect
1357 ;; Asynchronous connection
1359 (`failed
1360 ;; Asynchronous connection failed
1370 buffer))
1379 url-https-default-port)
1388 ;; Saw the end of the headers
1393 ;; We got back a headerless malformed response from the
1394 ;; server.
1401 :process proc
1404 ;; check certificate validity
1428 ;; We are performing an asynchronous connection, and a status change
1429 ;; has occurred.
1453 ;; Since Emacs 19/20 does not allow you to change the
1454 ;; `after-change-functions' hook in the midst of running them, we fake
1455 ;; an after change by hooking into the process filter and inserting
1456 ;; the data ourselves. This is slightly less efficient, but there
1457 ;; were tons of weird ways the after-change code was biting us in the
1458 ;; shorts.
1459 ;; FIXME this can probably be simplified since the above is no longer true.
1461 ;; Sometimes we get a zero-length data chunk after the process has
1462 ;; been changed to 'free', which means it has no buffer associated
1463 ;; with it. Do nothing if there is no buffer, or 0 length data.
1467 (url-http-debug "Calling after change function `%s' for `%S'" url-http-after-change-function proc)
1476 ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
1477 ;;; file-name-handler stuff from here on out
1478 ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
1481 'symbol-value-in-buffer
1483 "Return the value of SYMBOL in BUFFER, or UNBOUND-VALUE if it is unbound."
1486 unbound-value
1511 nil ;dir / link / normal file
1514 nil nil nil ;atime ; mtime ; ctime
1529 "Return a property list describing options available for URL.
1530 This list is retrieved using the `OPTIONS' HTTP method.
1532 Property list members:
1534 methods
1535 A list of symbols specifying what HTTP methods the resource
1536 supports.
1538 dav
1539 A list of numbers specifying what DAV protocol/schema versions are
1540 supported.
1542 dasl
1543 A list of supported DASL search types supported (string form)
1545 ranges
1546 A list of the units available for use in partial document fetches.
1548 p3p
1549 The `Platform For Privacy Protection' description for the resource.
1550 Currently this is just the raw header contents. This is likely to
1551 change once P3P is formally supported by the URL package or
1552 Emacs/W3."
1560 ;; Only parse the options if we got a 2xx response code!
1566 ;; Figure out what methods are supported.
1569 options 'methods
1572 ;; Check for DAV
1575 options 'dav
1580 ;; Now for DASL
1583 options 'dasl
1586 ;; P3P - should get more detailed here. FIXME
1590 ;; Check for whether they accept byte-range requests.
1593 options 'ranges
1597 ))))
1599 options))
1601 ;; HTTPS. This used to be in url-https.el, but that file collides
1602 ;; with url-http.el on systems with 8-character file names.
1606 ;; FIXME what is the point of this alias being an autoload?
1607 ;; Trying to use it will not cause url-http to be loaded,
1608 ;; since the full alias just gets dumped into loaddefs.el.
1610 ;;;###autoload (autoload 'url-default-expander "url-expand")
1611 ;;;###autoload
1620 ;;;###autoload (autoload 'url-https "url-http")
1622 ;;;###autoload (autoload 'url-https-file-exists-p "url-http")
1624 ;;;###autoload (autoload 'url-https-file-readable-p "url-http")
1626 ;;;###autoload (autoload 'url-https-file-attributes "url-http")
1631 ;;; url-http.el ends here