Is it possible to get URL fragment parameters in C under glib ?
I've got a url like file://localhost/home/me/notepad.txt#line=100,2
What's the best way to get the parameters specified at the end of the url ?
-
1The relevant section of the GLib documentation suggests not; at least not in a handy do-it-for-you function.Shawn– Shawn2019-09-03 00:37:51 +00:00Commented Sep 3, 2019 at 0:37
-
Cheers, I guess they just implemented what they needed - seemed a bit weird there was nothing there.Stuart Axon– Stuart Axon2019-09-03 11:57:26 +00:00Commented Sep 3, 2019 at 11:57
Add a comment
|
4 Answers
There’s no single GLib function which will do what you want. If you can use libsoup (also part of the GNOME stack), then you can do it using SoupURI:
g_autoptr(SoupURI) uri = soup_uri_new (uri_string);
const gchar *fragment = soup_uri_get_fragment (uri);
That will set fragment to line=100,2. You’ll have to do further parsing of whatever your fragment format is, by hand. g_strsplit() would be useful for that.
Comments
Since GLib 2.66 (released Sep 10, 2020) it is possible to parse uris by using GUri eg. g_uri_parse()
Most other answers are dated before 2020 that's why they say it's not possible.
answered Oct 19, 2024 at 18:28
Nelson Benítez León
51.1k8 gold badges70 silver badges84 bronze badges
Comments
You may also take a look on the function parse_sftp_uri from gnome-terminal terminal-nautilus.c file. It can be easily adapted for general URIs.
Comments
Unsure if you mean to parse notepad.txt#line=100,2 or #line=100,2, nevertheless my answer should work in both cases.
You can use the strrchr() (man strrchr) function to get the last occurence of a character within a string.
Something like:
char *file;
file = strrchr(url, '/') + 1;
7 Comments
Philip Withnall
That won’t work if the fragment itself contains a
/.
fassn
I believe there can't be a '/' in a URL or else it's not the parameter
Philip Withnall
RFC 3986 explicitly allows
/ (and ?) in fragments. The syntax for a fragment is fragment = *( pchar / "/" / "?" ).fassn
That's a bit surprising to say the least, I was doing SEO and had to parse millions of URLs for analysis purposes and can't recall ever having this issue. Guess I was just lucky :) thanks for pointing that out!
Stuart Axon
Hi, it's the
line=100,2 I'd like to extract. |