IE in newer versions will accept this as well, but older versions used 3 or 4 forward slashes (can't remember exactly). Mozilla based browsers expect 5 forward slashes: 2 for belonging to the protocol, one for the root node and the final two for the UNC naming of the remote host. You may need to experiment a bit with the number of slashes. which are basically links using the file:// protocol but with a resource on a remote share.
Rudolfo wrote:If you say that you want to have your users modifying the original file and not a downloaded copy it makes only sense if you use UNC paths. It is not difficult to set this up, not in Internet Informaton Server and not in Apache. Remember DAV stands for "Distributed Authoring and Versioning".
On second thought: The scenario that you describe sounds very much like you'd better use a Webserver with WebDAV enabled. There is one tiny difference Windows Explorer ignores the Setting for the Value "Content Type" in the registry key ".odt", but for Internet Explorer it is relevant: On my system it is: "application/" (Not really sure about this, it could be that the Content Type is ignored by IE as well, if the file is not served via http:, but through file:) odt file in Windows Explorer and it opens in Writer it should work in IE as well.
In other words if you can double click on a. The same that is used by the File Manager WIndows Explorer. But stay away from backward slashes, they are wrong in URLs.įor file associations IE uses the configuration in the registry, HKEY_CLASSES_ROOT.
If you say that you want to have your users modifying the original file and not a downloaded copy it makes only sense if you use UNC paths.
0 kommentar(er)
