On Mon, Dec 18, 2017 at 1:25 PM, Kaartic Sivaraam <kaartic.sivar...@gmail.com> wrote: > From: Nicolas Morey-Chaisemartin <nmoreychaisemar...@suse.com> > [...] > resulted in the following error,
s/resulted/results/ > curl_easy_perform() failed: URL using bad/illegal format or missing URL > > That was a consequence of the not URI encoding the folder portion of s/That was/This is/ s/the not/not/ s/URI encoding/URI-encoding/ > the URL which contained characters such as '[' which are not s/contained/contains/ > allowed in a URI. According to RFC3986, these characters should be > "URI encoded". > > So, URI encode the folder portion of the URL to ensure it doesn't > contain characters that aren't allowed in a URI. > > Reported-by: Doron Behar <doron.be...@gmail.com> > Signed-off-by: Nicolas Morey-Chaisemartin <nmoreychaisemar...@suse.com> > --- > > I came across the same issue that lead to this patch recently and found > that this patch didn't make it in. So, I thought I could help out and > hence this v2. Thanks for taking up the slack.
