On Sat, 7 Dec 2024 at 16:21, Chuck Lever <chuck.lever@xxxxxxxxxx> wrote: > >> IMO, using a URL parser library might be better for us in the > >> long run (eg, more secure) than adding our own little > >> implementation. FedFS used liburiparser. > > > > The liburiparser is a bit of an overkill, but I can look into it. > > Here's the point of using a library: > > A popular library implementation has been very well reviewed and is > used by a number of applications. That gives a high degree of confidence > that there are fewer bugs (in particular, security-related bugs). The > library might be actively maintained, and so we don't have to do that > work. > > Something like liburiparser might be more than we need for this > particular job, but code re-use is pretty foundational. If liburiparser > isn't a good fit, look for something that is a better fit. I can have a stab at this unless Roland objects Ced -- Cedric Blancher <cedric.blancher@xxxxxxxxx> [https://plus.google.com/u/0/+CedricBlancher/] Institute Pasteur
