Re: [Qemu-devel] [PATCH 1/4] curl: Fix parsing of readahead option from filename

2014-05-14 Thread Eric Blake
On 05/14/2014 10:00 AM, Matthew Booth wrote: > On 13/05/14 13:29, Eric Blake wrote: >> On 05/08/2014 02:42 AM, Matthew Booth wrote: >>> curl_parse_filename wasn't removing the option string from the >>> url, resulting in a 404. >>> >>> This change is a rewrite of the previous parsing behaviour, and

Re: [Qemu-devel] [PATCH 1/4] curl: Fix parsing of readahead option from filename

2014-05-14 Thread Matthew Booth
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 13/05/14 13:29, Eric Blake wrote: > On 05/08/2014 02:42 AM, Matthew Booth wrote: >> curl_parse_filename wasn't removing the option string from the >> url, resulting in a 404. >> >> This change is a rewrite of the previous parsing behaviour, and >>

Re: [Qemu-devel] [PATCH 1/4] curl: Fix parsing of readahead option from filename

2014-05-13 Thread Eric Blake
On 05/08/2014 02:42 AM, Matthew Booth wrote: > curl_parse_filename wasn't removing the option string from the url, > resulting in a 404. > > This change is a rewrite of the previous parsing behaviour, and > also changes the option syntax. The new syntax is: > > http://example.com/path?query[ssl

[Qemu-devel] [PATCH 1/4] curl: Fix parsing of readahead option from filename

2014-05-08 Thread Matthew Booth
curl_parse_filename wasn't removing the option string from the url, resulting in a 404. This change is a rewrite of the previous parsing behaviour, and also changes the option syntax. The new syntax is: http://example.com/path?query[sslverify=off:readahead=64k] The new syntax is well defined a