David Sheets

I talked with someone on IRC a few days back who was still experiencing this problem (and pointed to this bug). I've not tried to reproduce this recently as I...

@amirmc that is an ocaml-sodium issue rather than a `libffi` issue. ocaml-sodium 0.5.0 does not use `libffi`. If you could report this to https://github.com/dsheets/ocaml-sodium that would be great.

Please include information regarding your OS, homebrew installation, libsodium installation, and `cc` version when reporting to ocaml-sodium.

This breaking change will occur in 2.0 which isn't scheduled yet. 1.9 is the next release imminently.

In fact, 1.9 will (finally) expose the `uri.services_full` findlib package and `Uri_services_full` module companions to the `uri.services` package and `Uri_services` module.

A prime test for this functionality will be the original segment-of-only-%2F of 37771d7c7a223b6302c961e7d96219ef729d1ced. Other segments containing `%2F` work fine.

You can achieve most of that with `resolve`: ``` ocaml # Uri.(resolve "" (of_string "/foo/bar/") (of_string "baz/quux/"));; - : Uri.t = /foo/bar/baz/quux # Uri.(resolve "" (of_string "/foo/bar/") (of_string "/baz/quux"));; -...

I do think more needs to be done to make users aware of the power of `resolve`. This issue is about exposing the structure of the path component directly as...

Thanks for taking the initiative on this. I would like to find a solution that didn't require exceptions or schemes-which-aren't-schemes. In particular, it would be nice to override encoding of...

Ok. Sorry for the delay. I will take a look at this soon. I have been traveling and am now quite crunched and jetlagged.