Re: imap-send with gmail: curl_easy_perform() failed: URL using bad/illegal format or missing URL
- From
Nicolas Morey-Chaisemartin <nicolas@morey-chaisemartin.com>
- Date
- Nov 30, 2017, 09:51 UTC
- Message-ID
- <44bbb765-fb0d-5b80-c697-76a9b6ff0811@morey-chaisemartin.com>
- In-Reply-To
- <alpine.DEB.2.20.1711301041250.30591@tvnag.unkk.fr>
Le 30/11/2017 à 10:46, Daniel Stenberg a écrit :
Show 11 quoted lines
> On Thu, 30 Nov 2017, Nicolas Morey-Chaisemartin wrote: > >> This is due to the weird "[Gmail]" prefix in the folder. >> I tried manually replacing it with: >> folder = %5BGmail%5D/Drafts >> in .git/config and it works. >> >> curl is doing some fancy handling with brackets and braces. It make sense for multiple FTP downloads like ftp://ftp.numericals.com/file[1-100].txt, not in our case. The curl command line has a --globoff argument to disable this "regexp" support and it seems to fix the gmail case. However I couldn't find a way to change this value through the API... > > That's just a feature of the command line tool, "globbing" isn't a function provided by the library. libcurl actually "just" expects a plain old URL. >
Yep that what I figured looking a bit further in the code.
Show 6 quoted lines
> But with the risk of falling through the cracks into the rathole that is "what is a URL" (I've blogged about the topic several times in the past and I will surely do it again in the future): > > A "legal" URL (as per RFC 3986) does not contain brackets, such symbols should be used URL encoded: %5B and %5D. > > This said: I don't know exactly why brackets cause a problem in this case. It could still be worth digging into and see if libcurl could deal with them better here... >
It would make sense to have a way to ask libcurl to URI encode for us. I'm guessing there's already the code for that somewhere in curl and we would be wise to use it. But to work wqith older version we'll have to do it ourselves anyway.
Nicolas