-
Notifications
You must be signed in to change notification settings - Fork 475
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
relativeTo issue with empty folder #230
Comments
All clients I know translate I have not found anything in RFC 3986 that mandates this behavior. In fact I have not found any mention of
Here's a good summary on the behavior of Maybe we should talk about the semantics of your |
Well you are right, currently i have the So far I tested the code i posted in Chrome and was surprised to get So far i noticed the also google used the |
Does that mean we can close this issue now? |
Feel free to close this ticket, as I found the solution for me to use absolute URIs,which works for our project. |
using the url resolution of URL in Chrome I can see the following happening, suggesting that URI.js may indeed be a bit overzealous in normalizing paths: var url = new URL('../../d', 'https://google.com/a//b/c');
ulr.pathname === '/a/d' where URI.js behaves as follows: var url = new URI('../../d', 'https://google.com/a/b/c');
url.pathname() === '/d' Simply removing the |
I have an issue with generating an relative url where the current browsers url contains an empty folder:
The problem is that
normalizePath
convert'/a//c/d'
to'/a/c/d'
. Maybe you can find a solution for me?The text was updated successfully, but these errors were encountered: