-
Notifications
You must be signed in to change notification settings - Fork 170
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
More robust handling of paths beginning with // #308
Comments
Indeed you are correct. I am preparing a patch now. |
#309 fixes this issue. When that PR is merged, this issue will close. Thanks for reporting the problem! |
The fix does not seem to handle query params correctly, i.e. with the following url:
the path obtained with |
Indeed. :-( Sorry about that. It's the same problem as mirage/irmin#187 (comment). |
I'm trying to fix it. |
Here is a PR: #317 |
Hello,
When an uri such as
http://localhost//foo/bar
is requested,Uri.of_string
is used on the requested path, i.e.//foo/bar
, which returns an uri with path/bar
, because it handles the whole string as a uri. This should be parsed as a path, to handle "incorrect" paths beginning with "//".The call to
Uri.of_string
is here: https://github.com/mirage/ocaml-cohttp/blob/master/lib/request.ml#L113The text was updated successfully, but these errors were encountered: