So, we have some publishers in our department who have a passion for interlinking their MS Office documents (Word and Excel mainly) with relative hyperlinks. Then they publish them on our intranet website.
EDIT - I'm clarifying the issue cause the two answers missed the point.
In Excel and other Office documents, the hyperlinks are relatively pathed, and they do not include any explicit protocol.
When opened from the file system (Windows Explorer) these paths work (as expected).
When a hyperlink to this document is selected from a webpage, all browsers prompt the user to Open or Save the file. In all cases I am discussing here, the user is clicking "Open".
In Firefox, Chrome, and Opera, the Excel application is opened, and the relative links now use the
file://protocol and attempt to relative path from the cached copy. They are broken as expected, as the linked files do not exist in cache.
However, when opened from the Internet Explorer browser, the Excel client is launched, but floating over the hyperlinks, they are fully qualified addresses using the
http://protocol, as if the file was being served up by IIS like a web page.
So yes... it is something about the Micrsoft products (IIS, IE, and/or Office) and how they work together.
My question is How and Why would Excel be able to map the relatively pathed hyperlinks within itself to the fully qualified web address of where it was linked from?