Enumeration (GI Flags)

GLib-2.0GLibUriFlagsSince 2.66

Flags that describe a URI.

When parsing a URI, if you need to choose different flags based on the type of URI, you can use g_uri_peek_scheme() on the URI string to check the scheme first, and use that to decide what flags to parse it with.

2.66

Index

Enumeration Members

ENCODED: number

When parsing a URI, this indicates that %-encoded characters in the userinfo, path, query, and fragment fields should not be decoded. (And likewise the host field if GLib.UriFlags.NON_DNS is also set.) When building a URI, it indicates that you have already %-encoded the components, and so GLib.Uri should not do any encoding itself.

ENCODED_FRAGMENT: number

Same as GLib.UriFlags.ENCODED, for the fragment only.

ENCODED_PATH: number

Same as GLib.UriFlags.ENCODED, for the path only.

ENCODED_QUERY: number

Same as GLib.UriFlags.ENCODED, for the query field only.

HAS_AUTH_PARAMS: number

The userinfo may contain additional authentication-related parameters, which will be separated from the username and/or password by ;.

HAS_PASSWORD: number

The userinfo field may contain a password, which will be separated from the username by :.

NON_DNS: number

The host component should not be assumed to be a DNS hostname or IP address (for example, for smb URIs with NetBIOS hostnames).

NONE: number

No flags set.

PARSE_RELAXED: number

Parse the URI more relaxedly than the RFC 3986 grammar specifies, fixing up or ignoring common mistakes in URIs coming from external sources. This is also needed for some obscure URI schemes where ; separates the host from the path. Don’t use this flag unless you need to.

SCHEME_NORMALIZE: number

A scheme-based normalization will be applied. For example, when parsing an HTTP URI changing omitted path to / and omitted port to 80; and when building a URI, changing empty path to / and default port 80). This only supports a subset of known schemes. (Since: 2.68)