New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

expose URL parser #2412

Closed
lambdafu opened this Issue Mar 20, 2018 · 1 comment

Comments

Projects
None yet
2 participants
@lambdafu
Copy link

lambdafu commented Mar 20, 2018

Does libcurl expose the URL parser within curl? Using a different URL parser can lead to security problems, for example when matching the target domain (see https://docs.google.com/presentation/d/e/2PACX-1vSTFsJ9t0DatXbjmEGL8sKxt53gf6a1djHp_8Wbj2ZeTB6IfR-HsRD537-L5PgzVrs97bJu1tzJ1Smo/pub?start=false&loop=false&delayms=60000&slide=id.g32d0ed6ec2_0_41).

It would be good if libcurl could expose the URL parser, so it can be reused and/or tested against alternative implementations.

@bagder

This comment has been minimized.

Copy link
Member

bagder commented Mar 20, 2018

This is an issue tracker, not a question or support forum. We have dedicated mailing lists for that.

We've had requests for URL parsing APIs for a long time and I would like to see it added, but so far nobody has done the necessary work...

@bagder bagder closed this Mar 20, 2018

@lock lock bot locked as resolved and limited conversation to collaborators Jun 18, 2018

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.