MacOS creates a new mount on AFP path calls
- by jAndy
Hi Folks,
following scenario:
In my webapp, my customers are using Firefox as target browser. They have the need to open afp:// folders via Javascript. To make a long story short, this really works. You need to setup Firefox with about:config and set the value network.protocol-handler.external.afp to true.
What happens then, the operating system (OSX) takes care of that path and it correctly opens a Finder window.
The problem:
OSX does create a new mount every time. It cannot distinct between afp://host/path/111 and afp://host/path/222 for instance.
Furthermore, even if the afp path is 100% identical a new mount is created. It looks like this is the default behavior from OSX regardless of Firefox.
So, is there any chance I can tell OSX not to create a new mount for some sub directorys which should get access over afp:// ?
update:
It looks like, there are OSX applications which can change the default behavior for network protocols. So you can change "somewhere" which application OSX should call for a protocol. If that is true, wouldn't it be possible to create a script which just opens the local path without a afp:// prefix ?
The question here is, where is that configuration (?) to tell OSX which application to use for specific protocol. Any help welcome!
