cd076cd085
That is a legal url, but parseUrl parses it to "/c:/path" which is not a valid path on Windows. So as a workaround, use parseURIPortable everywhere, which removes the leading slash when run on windows. Note that if an url is parsed like this and then serialized back to a string, it will be different from the input. Which could potentially be a problem, but is probably not in practice. An alternative way to do it would be to have an uriPathPortable that fixes up the path after parsing. But it would be harder to make sure that is used everywhere, since uriPath is also used when constructing an URI. It's also worth noting that System.FilePath.normalize "/c:/path" yields "c:/path". The reason I didn't use it is that it also may change "/" to "\" in the path and I wanted to keep the url changes minimal. Also noticed that convertToWindowsNativeNamespace handles "/c:/path" the same as "c:/path". Sponsored-By: the NIH-funded NICEMAN (ReproNim TR&D3) project |
||
|---|---|---|
| .. | ||
| AWS.hs | ||
| Delete.hs | ||
| Edit.hs | ||
| Fsck.hs | ||
| IA.hs | ||
| Local.hs | ||
| Pairing.hs | ||
| Preferences.hs | ||
| Ssh.hs | ||
| Unused.hs | ||
| Upgrade.hs | ||
| WebDAV.hs | ||