diff options
author | Patrick Griffis <pgriffis@igalia.com> | 2020-10-26 14:33:44 -0500 |
---|---|---|
committer | Patrick Griffis <pgriffis@igalia.com> | 2020-11-06 15:32:17 -0600 |
commit | 9da213ea34b95d0c4387f593bf277a4a6b9a68d1 (patch) | |
tree | 0b7854579391c613a40ac8fd17a6fc90b8239ef4 | |
parent | 64f478dca367cc263332e46051a10096cab3f501 (diff) | |
download | glib-wip/tingping/guri-normalize.tar.gz |
docs: Add note about uri normalization for equalitywip/tingping/guri-normalize
-rw-r--r-- | glib/guri.c | 11 |
1 files changed, 6 insertions, 5 deletions
diff --git a/glib/guri.c b/glib/guri.c index c5399d7f3..ceed7133d 100644 --- a/glib/guri.c +++ b/glib/guri.c @@ -132,11 +132,12 @@ * * Note that there is no `g_uri_equal ()` function, because comparing * URIs usefully requires scheme-specific knowledge that #GUri does - * not have. For example, `http://example.com/` and - * `http://EXAMPLE.COM:80` have exactly the same meaning according - * to the HTTP specification, and `data:,foo` and - * `data:;base64,Zm9v` resolve to the same thing according to the - * `data:` URI specification. + * not have. #GUri can help with normalization if you use the various + * encoded #GUriFlags 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. * * Since: 2.66 */ |