I've found that if the host machine has a directory with an apostrophe, the OS X client will only show the name up to (but not including) the apostrophe in the mounted filesystem. This means when you try to enter the directory, OS X requests the truncated name (which doesn't exist on the server) and gets an access error. For example, a directory named "I'm sure this will work" shows up on the Mac as "I". Apparently apostrophes are not encoded by encodeURI, and OS X needs them to be encoded.
Apostrophes break OS X client, apparently. This fixes #52 by explicit…
…ly encoding apostrophes as well.
Upon further testing, found that ampersands and several other charact…
…ers break the OS X client as well. Changed my approach to completely escape all path fragments, and this seems to be working for every file I throw at it. Fixes #52
I spoke too soon. Previous commit reintroduced the problem with quote…
… marks while fixing most other characters. Forgot to go back and test the original problem. This has been tested with quote marks, double quote marks, ampersands, dashes, spaces, etc. Fixes #52
any explanation why this is not merged yet? Is the fix invalid or just missing some tests?
I can reproduce this with OSX Mountain Lion and latest master.