Posted by Philip Herlihy on January 13, 2005, 9:37 pm
Please log in for more thread options
I'm using a number of hyperlinks on an Intranet I'm developing which refer
to documents on a network server. The URLs I'm using have the form:
file://<server>/<path>/<file>.pdf
<server> is an UNC path, like: hostname
They work perfectly in IE, but not in Opera or Firefox. I can't see any
reason why not - is the form correct? Any other ideas?
--
####################
## PH, London
####################
(crossposted: follow-up to: uk.net.web.authoring)
Posted by Jukka K. Korpela on January 13, 2005, 10:10 pm
Please log in for more thread options
> I'm using a number of hyperlinks on an Intranet I'm developing which
> refer to documents on a network server. The URLs I'm using have the
> form:
> file://<server>/<path>/<file>.pdf
>
> <server> is an UNC path, like: hostname
>
> They work perfectly in IE, but not in Opera or Firefox. I can't see
> any reason why not - is the form correct? Any other ideas?
There is no specification of how file: URLs _should_ work, except for their
overall syntax and the statement that they refer to files in a system-
dependent manner. For a treatise on file: URLs, see
http://www.cs.tut.fi/~jkorpela/fileurl.html
With the given information, it is hardly possible to say what causes the
_browser_ differences. It might be the reverse solidus (backslash)
characters, which violate URL syntax.
Followup-To overridden - I can't see much point in asking in a random set
of newsgroups, three international and one national, and setting followups
to the _national_ group. Of course _none_ of the groups was really the
right one - as so often in crossposting. Hence followups now set to poster.
This means you should think what your problem really is, and start over
after selecting the right group.
--
Yucca, http://www.cs.tut.fi/~jkorpela/ Pages about Web authoring: http://www.cs.tut.fi/~jkorpela/www.html
Posted by Philip Herlihy on January 19, 2005, 8:05 pm
Please log in for more thread options
> There is no specification of how file: URLs _should_ work, except for
> their
> overall syntax and the statement that they refer to files in a system-
> dependent manner. For a treatise on file: URLs, see
> http://www.cs.tut.fi/~jkorpela/fileurl.html >
> With the given information, it is hardly possible to say what causes the
> _browser_ differences. It might be the reverse solidus (backslash)
> characters, which violate URL syntax.
>
> Followup-To overridden - I can't see much point in asking in a random set
> of newsgroups, three international and one national, and setting followups
> to the _national_ group. Of course _none_ of the groups was really the
> right one - as so often in crossposting. Hence followups now set to
> poster.
> This means you should think what your problem really is, and start over
> after selecting the right group.
>
> --
> Yucca, http://www.cs.tut.fi/~jkorpela/ > Pages about Web authoring: http://www.cs.tut.fi/~jkorpela/www.html >
Thanks - that's a very useful account. In my case, the browsers appear to
be refusing to follow file:// links from a page fetched using http://,
except for IE, which is happy to oblige. The files are PDFs on a private
network/intranet. Nevertheless, it probably makes sense to serve them from
the webserver in future.
I note your comment on crossposting. One difficulty is framing a sensible
question and another is knowing where to ask - hence the temptation to
crosspost. I was once severely scolded for not putting a "Followup" group
(and yes, that one was chosen at random). Which would you say would have
been the correct single group?
--
####################
## PH, London
####################
Posted by Gervase Markham on January 20, 2005, 10:52 am
Please log in for more thread options
Philip Herlihy wrote:
> Thanks - that's a very useful account. In my case, the browsers appear to
> be refusing to follow file:// links from a page fetched using http://,
This is security behaviour, working as designed.
If you really want to turn it off, set the "security.checkloaduri" pref
to false.
XML Sitemap