On Wed, Aug 01, 2018 at 11:54:56PM -0500, Radu Hociung wrote:
> On 01/08/2018 5:17 PM, Daniel Stenberg wrote:
> > a "URL handling" API in libcurl
>
> This wheel has already been invented. [1]

The main point of having a libcurl API has to do with reducing security issues
due to differences in URL parsing between libcurl and applications. Pointing
people at another parser won't solve that problem, unless libcurl were
rewritten to use that parser itself. That may actually be a solution, but we'd
have to be careful that using an external parser doesn't introduce regressions.
What worries me is the statement that this particular library is "strictly RFC
3986 compliant" which means that the various quirks added to libcurl's parser
to conform to WhatWG and browser implementation will disappear and introduce
such regressions. An external library would also hamper libcurl's ability to
fix problems or introduce new URL schemes (standardized or not) in the future.
-------------------------------------------------------------------
Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library
Etiquette: https://curl.haxx.se/mail/etiquette.html
Received on 2018-08-02