Comments (9)
See curl/curl#13396
from trurl.
I think this is a limitation of libcurl's urlapi
from trurl.
From the manual for curl_url_get:
CURLUPART_QUERY
The initial question mark that denotes the beginning of the query part is a delimiter only. It is not part of the query contents.
A not-present query will lead part to be set to NULL. A zero-length query will lead part to be set to a zero-length string.
The query part will also get pluses converted to space when asked to URL decode on get with the CURLU_URLDECODE bit.
from trurl.
I was mainly referring to it normalising scheme://host/path/?
as scheme://host/path/
even though it can distinguish no query and empty query. But yeah, also note that it can only do that for queries, not fragments.
$ ./foo 'scheme://host/path/'
in: scheme://host/path/
out: scheme://host/path/
query: NULL
frag: NULL
$ ./foo 'scheme://host/path/?'
in: scheme://host/path/?
out: scheme://host/path/
query:
frag: NULL
$ ./foo 'scheme://host/path/#'
in: scheme://host/path/#
out: scheme://host/path/
query: NULL
frag: NULL
$ ./foo 'scheme://host/path/?#'
in: scheme://host/path/?#
out: scheme://host/path/
query:
frag: NULL
$ ./foo 'scheme://host/path/?#hello'
in: scheme://host/path/?#hello
out: scheme://host/path/#hello
query:
frag: hello
$ ./foo 'scheme://host/path/?hello#'
in: scheme://host/path/?hello#
out: scheme://host/path/?hello
query: hello
frag: NULL
libcurl always normalises empty query/fragment as no query/fragment; and it does not provide a way to distinguish empty fragment from no fragment.
#include <curl/curl.h>
int main(int const argc, char const *const argv[])
{
if (argc != 2)
return 1;
CURLU *const uh = curl_url();
curl_url_set(uh, CURLUPART_URL, argv[1],
CURLU_NON_SUPPORT_SCHEME|
CURLU_GUESS_SCHEME|
CURLU_URLENCODE);
char *url;
curl_url_get(uh, CURLUPART_URL, &url, CURLU_DEFAULT_PORT);
char *query;
curl_url_get(uh, CURLUPART_QUERY, &query, CURLU_DEFAULT_PORT);
char *frag;
curl_url_get(uh, CURLUPART_FRAGMENT, &frag, CURLU_DEFAULT_PORT);
printf("in:\t%s\n"
"out:\t%s\n"
"query:\t%s\n"
"frag:\t%s\n",
argv[1], url, query ? query : "NULL", frag ? frag : "NULL");
curl_free(url);
curl_free(query);
curl_free(frag);
curl_url_cleanup(uh);
return 0;
}
from trurl.
Yes, I was hoping that it could be reflected in trurl as well. (and curl
itself is in the good bucket for that :))
Thank you for providing also the full demo code :)
from trurl.
With libcurl supporting empty queries and fragments now, how do you think we should enable this in trurl?
from trurl.
Probably would be useful to have --unset
to clean up query and frag, and make so trurl scheme://host/path --set query=""
would return scheme://host/path?
.
and have --get {component} return nothing if not present and the empty line if present.
But those would be breaking changes.
from trurl.
But those would be breaking changes.
I think we are free to do breaking changes if we want, at least before an official version one. I think the bigger problem is that they would work differently depending on what the underlying libcurl in use supports...
from trurl.
another (clunky) solution may be a new flag--allow-empty
for --get
and --set
?
or something clever with the the modifiers in the get brackets --get
, something like --get "{empty:query} {empty:fragment}"
? Im not sure how this would work with setting empty fields though.
from trurl.
Related Issues (20)
- test fails if built against libcurl 8.3.0 HOT 4
- new version release with recent fixes? HOT 1
- About the release scheme HOT 6
- Components with control characters don't appear in `--json` output, and non-urlencoded `--get` fails HOT 3
- [FR] allow JSON input in the same form as JSON parts output HOT 3
- incorrect decode of %3d as = character in query string leads to out of bound reads
- incorrect decode of %00 in query string leads to out of bound reads when printing the param key HOT 2
- incorrect handling of strings with null characters in memdupdec causes out of bounds write to adjacent memory region HOT 1
- 103: failed 'https://räksmörgås.se' -g '{default:puny:url}' HOT 7
- Allow bundling options and arguments
- Read from stdin by default HOT 2
- -s host=[::1] fails HOT 1
- Does 'https://curl.se/?&&&' really have a blank query?
- Get path components by index / json array HOT 8
- support --option=[value] style of command line parsing? HOT 1
- Option to specify default scheme HOT 2
- bug where --iterate causes --append to be duplicated for each iteration HOT 3
- `--get "{query:$NAME}"` only returns the first match HOT 15
- `--set "query:$NAME=$VALUE"` is not supported HOT 13
- output errors do not lead to a non-zero exit code HOT 9
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from trurl.