Lines Matching refs:URL
12 single: URL
13 pair: URL; parsing
14 pair: relative; URL
18 This module defines a standard interface to break Uniform Resource Locator (URL)
20 combine the components back into a URL string, and to convert a "relative URL"
21 to an absolute URL given a "base URL."
24 Resource Locators. It supports the following URL schemes: ``file``, ``ftp``,
31 categories: URL parsing and URL quoting. These are covered in detail in
34 URL Parsing
37 The URL parsing functions focus on splitting a URL string into its components,
38 or on combining URL components into a URL string.
42 Parse a URL into six components, returning a 6-tuple. This corresponds to the
43 general structure of a URL: ``scheme://netloc/path;parameters?query#fragment``.
64 input is presumed to be a relative URL and thus to start with
82 used only if the URL does not specify one. It should be the same type
97 | :attr:`scheme` | 0 | URL scheme specifier | *scheme* parameter |
121 an invalid port is specified in the URL. See section
129 ``#``, ``@``, or ``:`` will raise a :exc:`ValueError`. If the URL is
133 Added IPv6 URL parsing capabilities.
136 The fragment is now parsed for all URL schemes (unless *allow_fragment* is
220 Construct a URL from a tuple as returned by ``urlparse()``. The *parts*
222 different, but equivalent URL, if the URL that was parsed originally had
229 This is similar to :func:`urlparse`, but does not split the params from the URL.
230 This should generally be used instead of :func:`urlparse` if the more recent URL
232 of the URL (see :rfc:`2396`) is wanted. A separate function is needed to
242 | :attr:`scheme` | 0 | URL scheme specifier | *scheme* parameter |
263 an invalid port is specified in the URL. See section
271 ``#``, ``@``, or ``:`` will raise a :exc:`ValueError`. If the URL is
286 complete URL as a string. The *parts* argument can be any five-item
287 iterable. This may result in a slightly different, but equivalent URL, if the
288 URL that was parsed originally had unnecessary delimiters (for example, a ?
294 Construct a full ("absolute") URL by combining a "base URL" (*base*) with
295 another URL (*url*). Informally, this uses components of the base URL, in
297 path, to provide missing components in the relative URL. For example:
308 If *url* is an absolute URL (that is, starting with ``//`` or ``scheme://``),
339 | :attr:`url` | 0 | URL with no fragment | empty string |
355 The URL parsing functions were originally designed to operate on character
358 URL parsing functions in this module all operate on :class:`bytes` and
371 :class:`bytes`, all return values from URL parsing functions provide
383 bytes to characters before invoking the URL parsing methods.
385 The behaviour described in this section applies only to the URL parsing
386 functions. The URL quoting functions use their own rules when producing
388 individual URL quoting functions.
391 URL parsing functions now accept ASCII encoded byte sequences
407 Return the re-combined version of the original URL as a string. This may
408 differ from the original URL in that the scheme may be normalized to lower
414 made to the URL returned by this method.
481 URL Quoting
484 The URL quoting functions focus on taking program data and making it safe
485 for use as URL components by quoting special characters and appropriately
487 recreate the original data from the contents of a URL component if that
488 task isn't already covered by the URL parsing functions above.
494 function is intended for quoting the path section of URL. The optional *safe*
501 Moved from :rfc:`2396` to :rfc:`3986` for quoting URL strings. "~" is now
521 quoting HTML form values when building up a query string to go into a URL.
612 method can be used for generating query string for a URL or data for POST.
629 :rfc:`2732` - Format for Literal IPv6 Addresses in URL's.
636 :rfc:`2368` - The mailto URL scheme.
637 Parsing requirements for mailto URL schemes.
641 relative URL, including a fair number of "Abnormal Examples" which govern the
644 :rfc:`1738` - Uniform Resource Locators (URL)