:right-sidebar: True Uri =================================================================== .. currentmodule:: gi.repository.GLib .. versionadded:: 2.66 .. class:: Uri(*args, **kwargs) :no-contents-entry: The ``GUri`` type and related functions can be used to parse URIs into their components, and build valid URIs from individual components. Since ``GUri`` only represents absolute URIs, all ``GUri``\s will have a URI scheme, so :obj:`~gi.repository.GLib.Uri.get_scheme` will always return a non-``NULL`` answer. Likewise, by definition, all URIs have a path component, so :obj:`~gi.repository.GLib.Uri.get_path` will always return a non-``NULL`` string (which may be empty). If the URI string has an `‘authority’ component `__ (that is, if the scheme is followed by ``://`` rather than just ``:``\), then the ``GUri`` will contain a hostname, and possibly a port and ‘userinfo’. Additionally, depending on how the ``GUri`` was constructed/parsed (for example, using the ``G_URI_FLAGS_HAS_PASSWORD`` and ``G_URI_FLAGS_HAS_AUTH_PARAMS`` flags), the userinfo may be split out into a username, password, and additional authorization-related parameters. Normally, the components of a ``GUri`` will have all ``%``\-encoded characters decoded. However, if you construct/parse a ``GUri`` with ``G_URI_FLAGS_ENCODED``\, then the ``%``\-encoding will be preserved instead in the userinfo, path, and query fields (and in the host field if also created with ``G_URI_FLAGS_NON_DNS``\). In particular, this is necessary if the URI may contain binary data or non-UTF-8 text, or if decoding the components might change the interpretation of the URI. For example, with the encoded flag: .. code-block:: c :dedent: g_autoptr(GUri) uri = g_uri_parse ("http://host/path?query=http%3A%2F%2Fhost%2Fpath%3Fparam%3Dvalue", G_URI_FLAGS_ENCODED, &err); g_assert_cmpstr (g_uri_get_query (uri), ==, "query=http%3A%2F%2Fhost%2Fpath%3Fparam%3Dvalue"); While the default ``%``\-decoding behaviour would give: .. code-block:: c :dedent: g_autoptr(GUri) uri = g_uri_parse ("http://host/path?query=http%3A%2F%2Fhost%2Fpath%3Fparam%3Dvalue", G_URI_FLAGS_NONE, &err); g_assert_cmpstr (g_uri_get_query (uri), ==, "query=http://host/path?param=value"); During decoding, if an invalid UTF-8 string is encountered, parsing will fail with an error indicating the bad string location: .. code-block:: c :dedent: g_autoptr(GUri) uri = g_uri_parse ("http://host/path?query=http%3A%2F%2Fhost%2Fpath%3Fbad%3D%00alue", G_URI_FLAGS_NONE, &err); g_assert_error (err, G_URI_ERROR, G_URI_ERROR_BAD_QUERY); You should pass ``G_URI_FLAGS_ENCODED`` or ``G_URI_FLAGS_ENCODED_QUERY`` if you need to handle that case manually. In particular, if the query string contains ``=`` characters that are ``%``\-encoded, you should let :obj:`~gi.repository.GLib.Uri.parse_params` do the decoding once of the query. ``GUri`` is immutable once constructed, and can safely be accessed from multiple threads. Its reference counting is atomic. Note that the scope of ``GUri`` is to help manipulate URIs in various applications, following `RFC 3986 `__\. In particular, it doesn't intend to cover web browser needs, and doesn’t implement the `WHATWG URL `__ standard. No APIs are provided to help prevent `homograph attacks `__\, so ``GUri`` is not suitable for formatting URIs for display to the user for making security-sensitive decisions. Relative and absolute URIs -------------------------------------------------------------------------------- As defined in `RFC 3986 `__\, the hierarchical nature of URIs means that they can either be ‘relative references’ (sometimes referred to as ‘relative URIs’) or ‘URIs’ (for clarity, ‘URIs’ are referred to in this documentation as ‘absolute URIs’ — although `in contrast to RFC 3986 `__\, fragment identifiers are always allowed). Relative references have one or more components of the URI missing. In particular, they have no scheme. Any other component, such as hostname, query, etc. may be missing, apart from a path, which has to be specified (but may be empty). The path may be relative, starting with ``./`` rather than ``/``\. For example, a valid relative reference is ``./path?query``\, ``/?query#fragment`` or ``//example.com``\. Absolute URIs have a scheme specified. Any other components of the URI which are missing are specified as explicitly unset in the URI, rather than being resolved relative to a base URI using :obj:`~gi.repository.GLib.Uri.parse_relative`\. For example, a valid absolute URI is ``file:///home/bob`` or ``https://search.com?query=string``\. A ``GUri`` instance is always an absolute URI. A string may be an absolute URI or a relative reference; see the documentation for individual functions as to what forms they accept. Parsing URIs -------------------------------------------------------------------------------- The most minimalist APIs for parsing URIs are :obj:`~gi.repository.GLib.Uri.split` and :obj:`~gi.repository.GLib.Uri.split_with_user`\. These split a URI into its component parts, and return the parts; the difference between the two is that :obj:`~gi.repository.GLib.Uri.split` treats the ‘userinfo’ component of the URI as a single element, while :obj:`~gi.repository.GLib.Uri.split_with_user` can (depending on the :obj:`~gi.repository.GLib.UriFlags` you pass) treat it as containing a username, password, and authentication parameters. Alternatively, :obj:`~gi.repository.GLib.Uri.split_network` can be used when you are only interested in the components that are needed to initiate a network connection to the service (scheme, host, and port). :obj:`~gi.repository.GLib.Uri.parse` is similar to :obj:`~gi.repository.GLib.Uri.split`\, but instead of returning individual strings, it returns a ``GUri`` structure (and it requires that the URI be an absolute URI). :obj:`~gi.repository.GLib.Uri.resolve_relative` and :obj:`~gi.repository.GLib.Uri.parse_relative` allow you to resolve a relative URI relative to a base URI. :obj:`~gi.repository.GLib.Uri.resolve_relative` takes two strings and returns a string, and :obj:`~gi.repository.GLib.Uri.parse_relative` takes a ``GUri`` and a string and returns a ``GUri``\. All of the parsing functions take a :obj:`~gi.repository.GLib.UriFlags` argument describing exactly how to parse the URI; see the documentation for that type for more details on the specific flags that you can pass. If you need to choose different flags based on the type of URI, you can use :obj:`~gi.repository.GLib.Uri.peek_scheme` on the URI string to check the scheme first, and use that to decide what flags to parse it with. For example, you might want to use ``G_URI_PARAMS_WWW_FORM`` when parsing the params for a web URI, so compare the result of :obj:`~gi.repository.GLib.Uri.peek_scheme` against ``http`` and ``https``\. Building URIs -------------------------------------------------------------------------------- :obj:`~gi.repository.GLib.Uri.join` and :obj:`~gi.repository.GLib.Uri.join_with_user` can be used to construct valid URI strings from a set of component strings. They are the inverse of :obj:`~gi.repository.GLib.Uri.split` and :obj:`~gi.repository.GLib.Uri.split_with_user`\. Similarly, :obj:`~gi.repository.GLib.Uri.build` and :obj:`~gi.repository.GLib.Uri.build_with_user` can be used to construct a ``GUri`` from a set of component strings. As with the parsing functions, the building functions take a :obj:`~gi.repository.GLib.UriFlags` argument. In particular, it is important to keep in mind whether the URI components you are using are already ``%``\-encoded. If so, you must pass the ``G_URI_FLAGS_ENCODED`` flag. -------------------------------------------------------------------------------- Note that Windows and Unix both define special rules for parsing ``file://`` URIs (involving non-UTF-8 character sets on Unix, and the interpretation of path separators on Windows). ``GUri`` does not implement these rules. Use :obj:`~gi.repository.GLib.filename_from_uri` and :obj:`~gi.repository.GLib.filename_to_uri` if you want to properly convert between ``file://`` URIs and local filenames. URI Equality -------------------------------------------------------------------------------- Note that there is no ``g_uri_equal ()`` function, because comparing URIs usefully requires scheme-specific knowledge that ``GUri`` does not have. ``GUri`` can help with normalization if you use the various encoded :obj:`~gi.repository.GLib.UriFlags` as well as ``G_URI_FLAGS_SCHEME_NORMALIZE`` however it is not comprehensive. For example, ``data:,foo`` and ``data:;base64,Zm9v`` resolve to the same thing according to the ``data:`` URI specification which GLib does not handle. Methods ------- .. rst-class:: interim-class .. class:: Uri :no-index: .. classmethod:: build(scheme: str, userinfo: str | None, host: str | None, port: int, path: str, query: str | None = None, fragment: str | None = None) -> ~gi.repository.GLib.Uri Creates a new :obj:`~gi.repository.GLib.Uri` from the given components according to ``flags``\. See also :func:`~gi.repository.GLib.Uri.build_with_user`, which allows specifying the components of the "userinfo" separately. .. versionadded:: 2.66 :param scheme: the URI scheme :param userinfo: the userinfo component, or :const:`None` :param host: the host component, or :const:`None` :param port: the port, or ``-1`` :param path: the path component :param query: the query component, or :const:`None` :param fragment: the fragment, or :const:`None` .. classmethod:: build_with_user(scheme: str, user: str | None, password: str | None, auth_params: str | None, host: str | None, port: int, path: str, query: str | None = None, fragment: str | None = None) -> ~gi.repository.GLib.Uri Creates a new :obj:`~gi.repository.GLib.Uri` from the given components according to ``flags`` (:const:`~gi.repository.GLib.UriFlags.HAS_PASSWORD` is added unconditionally). The ``flags`` must be coherent with the passed values, in particular use ``%``\-encoded values with :const:`~gi.repository.GLib.UriFlags.ENCODED`. In contrast to :func:`~gi.repository.GLib.Uri.build`, this allows specifying the components of the ‘userinfo’ field separately. Note that ``user`` must be non-:const:`None` if either ``password`` or ``auth_params`` is non-:const:`None`. .. versionadded:: 2.66 :param scheme: the URI scheme :param user: the user component of the userinfo, or :const:`None` :param password: the password component of the userinfo, or :const:`None` :param auth_params: the auth params of the userinfo, or :const:`None` :param host: the host component, or :const:`None` :param port: the port, or ``-1`` :param path: the path component :param query: the query component, or :const:`None` :param fragment: the fragment, or :const:`None` .. classmethod:: error_quark() -> int .. classmethod:: escape_bytes(reserved_chars_allowed: str | None = None) -> str Escapes arbitrary data for use in a URI. Normally all characters that are not ‘unreserved’ (i.e. ASCII alphanumerical characters plus dash, dot, underscore and tilde) are escaped. But if you specify characters in ``reserved_chars_allowed`` they are not escaped. This is useful for the ‘reserved’ characters in the URI specification, since those are allowed unescaped in some portions of a URI. Though technically incorrect, this will also allow escaping nul bytes as ``%``00``\. .. versionadded:: 2.66 :param reserved_chars_allowed: a string of reserved characters that are allowed to be used, or :const:`None`. .. classmethod:: escape_string(reserved_chars_allowed: str | None, allow_utf8: bool) -> str Escapes a string for use in a URI. Normally all characters that are not "unreserved" (i.e. ASCII alphanumerical characters plus dash, dot, underscore and tilde) are escaped. But if you specify characters in ``reserved_chars_allowed`` they are not escaped. This is useful for the "reserved" characters in the URI specification, since those are allowed unescaped in some portions of a URI. .. versionadded:: 2.16 :param reserved_chars_allowed: a string of reserved characters that are allowed to be used, or :const:`None`. :param allow_utf8: :const:`True` if the result can include UTF-8 characters. .. method:: get_auth_params() -> str | None Gets ``uri``\'s authentication parameters, which may contain ``%``\-encoding, depending on the flags with which ``uri`` was created. (If ``uri`` was not created with :const:`~gi.repository.GLib.UriFlags.HAS_AUTH_PARAMS` then this will be :const:`None`.) Depending on the URI scheme, :func:`~gi.repository.GLib.Uri.parse_params` may be useful for further parsing this information. .. versionadded:: 2.66 .. method:: get_flags() -> ~gi.repository.GLib.UriFlags Gets ``uri``\'s flags set upon construction. .. versionadded:: 2.66 .. method:: get_fragment() -> str | None Gets ``uri``\'s fragment, which may contain ``%``\-encoding, depending on the flags with which ``uri`` was created. .. versionadded:: 2.66 .. method:: get_host() -> str | None Gets ``uri``\'s host. This will never have ``%``\-encoded characters, unless it is non-UTF-8 (which can only be the case if ``uri`` was created with :const:`~gi.repository.GLib.UriFlags.NON_DNS`). If ``uri`` contained an IPv6 address literal, this value will be just that address, without the brackets around it that are necessary in the string form of the URI. Note that in this case there may also be a scope ID attached to the address. Eg, ``fe80::1234%``em1`` (or ``fe80::1234%``25em1`` if the string is still encoded). .. versionadded:: 2.66 .. method:: get_password() -> str | None Gets ``uri``\'s password, which may contain ``%``\-encoding, depending on the flags with which ``uri`` was created. (If ``uri`` was not created with :const:`~gi.repository.GLib.UriFlags.HAS_PASSWORD` then this will be :const:`None`.) .. versionadded:: 2.66 .. method:: get_path() -> str Gets ``uri``\'s path, which may contain ``%``\-encoding, depending on the flags with which ``uri`` was created. .. versionadded:: 2.66 .. method:: get_port() -> int Gets ``uri``\'s port. .. versionadded:: 2.66 .. method:: get_query() -> str | None Gets ``uri``\'s query, which may contain ``%``\-encoding, depending on the flags with which ``uri`` was created. For queries consisting of a series of ``name=value`` parameters, :obj:`~gi.repository.GLib.UriParamsIter` or :func:`~gi.repository.GLib.Uri.parse_params` may be useful. .. versionadded:: 2.66 .. method:: get_scheme() -> str Gets ``uri``\'s scheme. Note that this will always be all-lowercase, regardless of the string or strings that ``uri`` was created from. .. versionadded:: 2.66 .. method:: get_user() -> str | None Gets the ‘username’ component of ``uri``\'s userinfo, which may contain ``%``\-encoding, depending on the flags with which ``uri`` was created. If ``uri`` was not created with :const:`~gi.repository.GLib.UriFlags.HAS_PASSWORD` or :const:`~gi.repository.GLib.UriFlags.HAS_AUTH_PARAMS`, this is the same as :func:`~gi.repository.GLib.Uri.get_userinfo`. .. versionadded:: 2.66 .. method:: get_userinfo() -> str | None Gets ``uri``\'s userinfo, which may contain ``%``\-encoding, depending on the flags with which ``uri`` was created. .. versionadded:: 2.66 .. classmethod:: is_valid(flags: ~gi.repository.GLib.UriFlags) -> bool Parses ``uri_string`` according to ``flags``\, to determine whether it is a valid `absolute URI <#relative-and-absolute-uris>`__\, i.e. it does not need to be resolved relative to another URI using :func:`~gi.repository.GLib.Uri.parse_relative`. If it’s not a valid URI, an error is returned explaining how it’s invalid. See :func:`~gi.repository.GLib.Uri.split`, and the definition of :obj:`~gi.repository.GLib.UriFlags`\, for more information on the effect of ``flags``\. .. versionadded:: 2.66 :param flags: flags for parsing ``uri_string`` .. classmethod:: join(scheme: str | None, userinfo: str | None, host: str | None, port: int, path: str, query: str | None = None, fragment: str | None = None) -> str Joins the given components together according to ``flags`` to create an absolute URI string. ``path`` may not be :const:`None` (though it may be the empty string). When ``host`` is present, ``path`` must either be empty or begin with a slash (``/``\) character. When ``host`` is not present, ``path`` cannot begin with two slash characters (``//``\). See `RFC 3986, section 3 `__\. See also :func:`~gi.repository.GLib.Uri.join_with_user`, which allows specifying the components of the ‘userinfo’ separately. :const:`~gi.repository.GLib.UriFlags.HAS_PASSWORD` and :const:`~gi.repository.GLib.UriFlags.HAS_AUTH_PARAMS` are ignored if set in ``flags``\. .. versionadded:: 2.66 :param scheme: the URI scheme, or :const:`None` :param userinfo: the userinfo component, or :const:`None` :param host: the host component, or :const:`None` :param port: the port, or ``-1`` :param path: the path component :param query: the query component, or :const:`None` :param fragment: the fragment, or :const:`None` .. classmethod:: join_with_user(scheme: str | None, user: str | None, password: str | None, auth_params: str | None, host: str | None, port: int, path: str, query: str | None = None, fragment: str | None = None) -> str Joins the given components together according to ``flags`` to create an absolute URI string. ``path`` may not be :const:`None` (though it may be the empty string). In contrast to :func:`~gi.repository.GLib.Uri.join`, this allows specifying the components of the ‘userinfo’ separately. It otherwise behaves the same. :const:`~gi.repository.GLib.UriFlags.HAS_PASSWORD` and :const:`~gi.repository.GLib.UriFlags.HAS_AUTH_PARAMS` are ignored if set in ``flags``\. .. versionadded:: 2.66 :param scheme: the URI scheme, or :const:`None` :param user: the user component of the userinfo, or :const:`None` :param password: the password component of the userinfo, or :const:`None` :param auth_params: the auth params of the userinfo, or :const:`None` :param host: the host component, or :const:`None` :param port: the port, or ``-1`` :param path: the path component :param query: the query component, or :const:`None` :param fragment: the fragment, or :const:`None` .. classmethod:: list_extract_uris() -> list[str] Splits an URI list conforming to the text/uri-list mime type defined in RFC 2483 into individual URIs, discarding any comments. The URIs are not validated. .. versionadded:: 2.6 .. classmethod:: parse(flags: ~gi.repository.GLib.UriFlags) -> ~gi.repository.GLib.Uri Parses ``uri_string`` according to ``flags``\. If the result is not a valid `absolute URI <#relative-and-absolute-uris>`__\, it will be discarded, and an error returned. .. versionadded:: 2.66 :param flags: flags describing how to parse ``uri_string`` .. classmethod:: parse_params(length: int, separators: str, flags: ~gi.repository.GLib.UriParamsFlags) -> dict[str, str] Many URI schemes include one or more attribute/value pairs as part of the URI value. This method can be used to parse them into a hash table. When an attribute has multiple occurrences, the last value is the final returned value. If you need to handle repeated attributes differently, use :obj:`~gi.repository.GLib.UriParamsIter`\. The ``params`` string is assumed to still be ``%``\-encoded, but the returned values will be fully decoded. (Thus it is possible that the returned values may contain ``=`` or ``separators``\, if the value was encoded in the input.) Invalid ``%``\-encoding is treated as with the :const:`~gi.repository.GLib.UriFlags.PARSE_RELAXED` rules for :func:`~gi.repository.GLib.Uri.parse`. (However, if ``params`` is the path or query string from a :obj:`~gi.repository.GLib.Uri` that was parsed without :const:`~gi.repository.GLib.UriFlags.PARSE_RELAXED` and :const:`~gi.repository.GLib.UriFlags.ENCODED`, then you already know that it does not contain any invalid encoding.) :const:`~gi.repository.GLib.UriParamsFlags.WWW_FORM` is handled as documented for :func:`~gi.repository.GLib.UriParamsIter.init`. If :const:`~gi.repository.GLib.UriParamsFlags.CASE_INSENSITIVE` is passed to ``flags``\, attributes will be compared case-insensitively, so a params string ``attr=123&Attr=456`` will only return a single attribute–value pair, ``Attr=456``\. Case will be preserved in the returned attributes. If ``params`` cannot be parsed (for example, it contains two ``separators`` characters in a row), then ``error`` is set and :const:`None` is returned. .. versionadded:: 2.66 :param length: the length of ``params``\, or ``-1`` if it is nul-terminated :param separators: the separator byte character set between parameters. (usually ``&``\, but sometimes ``;`` or both ``&;``\). Note that this function works on bytes not characters, so it can't be used to delimit UTF-8 strings for anything but ASCII characters. You may pass an empty set, in which case no splitting will occur. :param flags: flags to modify the way the parameters are handled. .. method:: parse_relative(uri_ref: str, flags: ~gi.repository.GLib.UriFlags) -> ~gi.repository.GLib.Uri Parses ``uri_ref`` according to ``flags`` and, if it is a `relative URI <#relative-and-absolute-uris>`__\, resolves it relative to ``base_uri``\. If the result is not a valid absolute URI, it will be discarded, and an error returned. .. versionadded:: 2.66 :param uri_ref: a string representing a relative or absolute URI :param flags: flags describing how to parse ``uri_ref`` .. classmethod:: parse_scheme() -> str | None Gets the scheme portion of a URI string. `RFC 3986 `__ decodes the scheme as: .. code-block:: :dedent: URI = scheme ":" hier-part [ "?" query ] [ "#" fragment ] Common schemes include ``file``\, ``https``\, ``svn+ssh``\, etc. .. versionadded:: 2.16 .. classmethod:: peek_scheme() -> str | None Gets the scheme portion of a URI string. `RFC 3986 `__ decodes the scheme as: .. code-block:: :dedent: URI = scheme ":" hier-part [ "?" query ] [ "#" fragment ] Common schemes include ``file``\, ``https``\, ``svn+ssh``\, etc. Unlike :func:`~gi.repository.GLib.Uri.parse_scheme`, the returned scheme is normalized to all-lowercase and does not need to be freed. .. versionadded:: 2.66 .. classmethod:: resolve_relative(uri_ref: str, flags: ~gi.repository.GLib.UriFlags) -> str Parses ``uri_ref`` according to ``flags`` and, if it is a `relative URI <#relative-and-absolute-uris>`__\, resolves it relative to ``base_uri_string``\. If the result is not a valid absolute URI, it will be discarded, and an error returned. (If ``base_uri_string`` is :const:`None`, this just returns ``uri_ref``\, or :const:`None` if ``uri_ref`` is invalid or not absolute.) .. versionadded:: 2.66 :param uri_ref: a string representing a relative or absolute URI :param flags: flags describing how to parse ``uri_ref`` .. classmethod:: split(flags: ~gi.repository.GLib.UriFlags) -> ~typing.Tuple[bool, str | None, str | None, str | None, int, str, str | None, str | None] Parses ``uri_ref`` (which can be an `absolute or relative URI <#relative-and-absolute-uris>`__\) according to ``flags``\, and returns the pieces. Any component that doesn't appear in ``uri_ref`` will be returned as :const:`None` (but note that all URIs always have a path component, though it may be the empty string). If ``flags`` contains :const:`~gi.repository.GLib.UriFlags.ENCODED`, then ``%``\-encoded characters in ``uri_ref`` will remain encoded in the output strings. (If not, then all such characters will be decoded.) Note that decoding will only work if the URI components are ASCII or UTF-8, so you will need to use :const:`~gi.repository.GLib.UriFlags.ENCODED` if they are not. Note that the :const:`~gi.repository.GLib.UriFlags.HAS_PASSWORD` and :const:`~gi.repository.GLib.UriFlags.HAS_AUTH_PARAMS` ``flags`` are ignored by :func:`~gi.repository.GLib.Uri.split`, since it always returns only the full userinfo; use :func:`~gi.repository.GLib.Uri.split_with_user` if you want it split up. .. versionadded:: 2.66 :param flags: flags for parsing ``uri_ref`` .. classmethod:: split_network(flags: ~gi.repository.GLib.UriFlags) -> ~typing.Tuple[bool, str | None, str | None, int] Parses ``uri_string`` (which must be an `absolute URI <#relative-and-absolute-uris>`__\) according to ``flags``\, and returns the pieces relevant to connecting to a host. See the documentation for :func:`~gi.repository.GLib.Uri.split` for more details; this is mostly a wrapper around that function with simpler arguments. However, it will return an error if ``uri_string`` is a relative URI, or does not contain a hostname component. .. versionadded:: 2.66 :param flags: flags for parsing ``uri_string`` .. classmethod:: split_with_user(flags: ~gi.repository.GLib.UriFlags) -> ~typing.Tuple[bool, str | None, str | None, str | None, str | None, str | None, int, str, str | None, str | None] Parses ``uri_ref`` (which can be an `absolute or relative URI <#relative-and-absolute-uris>`__\) according to ``flags``\, and returns the pieces. Any component that doesn't appear in ``uri_ref`` will be returned as :const:`None` (but note that all URIs always have a path component, though it may be the empty string). See :func:`~gi.repository.GLib.Uri.split`, and the definition of :obj:`~gi.repository.GLib.UriFlags`\, for more information on the effect of ``flags``\. Note that ``password`` will only be parsed out if ``flags`` contains :const:`~gi.repository.GLib.UriFlags.HAS_PASSWORD`, and ``auth_params`` will only be parsed out if ``flags`` contains :const:`~gi.repository.GLib.UriFlags.HAS_AUTH_PARAMS`. .. versionadded:: 2.66 :param flags: flags for parsing ``uri_ref`` .. method:: to_string() -> str Returns a string representing ``uri``\. This is not guaranteed to return a string which is identical to the string that ``uri`` was parsed from. However, if the source URI was syntactically correct (according to RFC 3986), and it was parsed with :const:`~gi.repository.GLib.UriFlags.ENCODED`, then :func:`~gi.repository.GLib.Uri.to_string` is guaranteed to return a string which is at least semantically equivalent to the source URI (according to RFC 3986). If ``uri`` might contain sensitive details, such as authentication parameters, or private data in its query string, and the returned string is going to be logged, then consider using :func:`~gi.repository.GLib.Uri.to_string_partial` to redact parts. .. versionadded:: 2.66 .. method:: to_string_partial(flags: ~gi.repository.GLib.UriHideFlags) -> str Returns a string representing ``uri``\, subject to the options in ``flags``\. See :func:`~gi.repository.GLib.Uri.to_string` and :obj:`~gi.repository.GLib.UriHideFlags` for more details. .. versionadded:: 2.66 :param flags: flags describing what parts of ``uri`` to hide .. classmethod:: unescape_bytes(length: int, illegal_characters: str | None = None) -> ~gi.repository.GLib.Bytes Unescapes a segment of an escaped string as binary data. Note that in contrast to :func:`~gi.repository.GLib.Uri.unescape_string`, this does allow nul bytes to appear in the output. If any of the characters in ``illegal_characters`` appears as an escaped character in ``escaped_string``\, then that is an error and :const:`None` will be returned. This is useful if you want to avoid for instance having a slash being expanded in an escaped path element, which might confuse pathname handling. .. versionadded:: 2.66 :param length: the length (in bytes) of ``escaped_string`` to escape, or ``-1`` if it is nul-terminated. :param illegal_characters: a string of illegal characters not to be allowed, or :const:`None`. .. classmethod:: unescape_segment(escaped_string_end: str | None = None, illegal_characters: str | None = None) -> str | None Unescapes a segment of an escaped string. If any of the characters in ``illegal_characters`` or the NUL character appears as an escaped character in ``escaped_string``\, then that is an error and :const:`None` will be returned. This is useful if you want to avoid for instance having a slash being expanded in an escaped path element, which might confuse pathname handling. Note: ``NUL`` byte is not accepted in the output, in contrast to :func:`~gi.repository.GLib.Uri.unescape_bytes`. .. versionadded:: 2.16 :param escaped_string_end: Pointer to end of ``escaped_string``\, may be :const:`None` :param illegal_characters: An optional string of illegal characters not to be allowed, may be :const:`None` .. classmethod:: unescape_string(illegal_characters: str | None = None) -> str | None Unescapes a whole escaped string. If any of the characters in ``illegal_characters`` or the NUL character appears as an escaped character in ``escaped_string``\, then that is an error and :const:`None` will be returned. This is useful if you want to avoid for instance having a slash being expanded in an escaped path element, which might confuse pathname handling. .. versionadded:: 2.16 :param illegal_characters: a string of illegal characters not to be allowed, or :const:`None`.