For people who had problems with AFP URLs after updating to Snow Leopard, last week's Mac OS X 10.6.7 update returns AFP file sharing to the way it worked in Mac OS X 10.5.x and earlier. Apple said the reversion fixes a problem opening an AFP URL (apf://xxxx) that points to a file. The update also changes the AFP mount path to what it was before Snow Leopard. AFP URL's can be used in a web browser, the Mail application, the Finder's Go menu, and the mount_afp command in Terminal.
In Snow Leopard versions before 10.6.7, AFP URLs that include a filename would fail to open (afp://myserver.mydomain.com/Sharepoint/Folder/file.txt). Before Snow Leopard, and now with the 10.6.7 update, URLs ending in filenames will mount the sharepoint volume in the Finder. URLs ending in the folder will also mount the sharepoint.
In addition to being able to handle URLS that end in a filename, the fact that the sharepoint is mounted a change from Mac OS X v10.6 through 10.6.6, which mount the folder (not the sharepoint), if the URL ends with the folder.
Another change is the local path to a subdirectory in a mounted sharepoint volume. In Mac OS X 10.0 through 10.5.8, and now in 10.6.7, the path is
/Volumes/Sharepoint/Folder/.
In Mac OS X 10.6.0-10.6.6, this local path to the folder is /Volumes/Folder/. That's because the folder, not the sharepoint, is mounted.
It shouldn't affect compatibility with third-party products, which by now hand both Leopard and earlier and Snow Leopard.
" This does not appear to be significant. We have no preference between the two approaches to AFP mounts," said Reid Lewis, president of Group Logic, the developer of ExtremeZ-IP, an AFP server for Windows meant to serve Mac clients.
The Mac OS X 10.6.7 update also included a number of other unrelated bug fixes and improvements, including fixing an issue when dragging files or folders to the Trash from an NFS home directory. Mac OS X 10.6.7 also includes security patches.
If Mac OS X 10.6.7 fixes any of the Snow Leopard problems we've been reporting (such as slow SMB performance)