Skip to content
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

Extended-Length Path In Windows Encoded Differently Than Windows Path #25

Open
git-blame opened this issue Sep 19, 2018 · 2 comments
Open
Labels
enhancement New feature or request windows

Comments

@git-blame
Copy link

An extended-length path in windows is prepended with "\\?\" (for example \\?\c:\windows). As such, uriparser doesn't seem to recognize it as a windows path. It is encoded but not in a typical Windows way.

My current work-around is to remove "\\?\" before passing in the path to uriWindowsFilenameToUriStringA.

@hartwork
Copy link
Member

Hi!

I don't have Windows at hand to try this out easily. Could you point me to the authoritative documentation on these kinds of Network paths?

@hartwork hartwork added enhancement New feature or request windows labels Sep 19, 2018
@git-blame
Copy link
Author

Check out https://docs.microsoft.com/en-us/windows/desktop/FileIO/naming-a-file specifically https://docs.microsoft.com/en-us/windows/desktop/FileIO/naming-a-file#maximum-path-length-limitation.

As an aside, the prefix can also be \\?\UNC\

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request windows
Projects
None yet
Development

No branches or pull requests

2 participants