Gravatar for achmedrauff.abdulrahim@3ds.com

Question by Achmed Rauff, Mar 31, 2015 5:31 AM

Cant download files from results sourced from networked file folder in Chrome and Firefox.

I am indexing files from shared folder in the local network. The issue is;

When using Chrome or Firefox, the files associated with the result displayed could not be downloaded. These are mostly Powerpoint files and only the cache version is displayed with a warning " Because of security restrictions, documents from file shares cannot be opened from a Web browser."

It works fine on IE.

Anyone knows what is causing the problem and how to fix it?

1 Reply
Gravatar for mlaporte@coveo.com

Answer by Martin Laporte, Mar 31, 2015 5:39 AM

All major browsers except Internet Explorer explicitly prevent opening files from file shares (e.g. through file://... urls). This is for security reasons, and sadly I'm not aware of any simple work around for this --- I remember we searched for quite a time and found nothing fully satisfying.

Gravatar for mlaporte@coveo.com

Comment by Martin Laporte, Mar 31, 2015 5:50 AM

One additional note: if you only need to download the files you can map an HTTP server in front of your file shares (using IIS), and then override the urls so that they use this instead. But you won't be able to open files and then save them back.

Gravatar for slangevin@coveo.com

Comment by Simon, Mar 31, 2015 9:09 AM

To add more details to mlaporte answer: http://source.coveo.com/2015/03/25/browserVSDIP/

Gravatar for achmedrauff.abdulrahim@3ds.com

Comment by Achmed Rauff, Apr 3, 2015 3:32 AM

I wonder why Coveo does not see this as a bug. It robs a lot of usability from users. Also we all know that IE is not a popular browser choice.

Gravatar for mlaporte@coveo.com

Comment by Martin Laporte, Apr 3, 2015 3:47 AM

We are well aware of the limitation but as I mentioned above it is caused by most browsers explicitly denying opening file share urls from web pages. There is no way for us to work around this, as it is a conscious choice made by the browser developers themselves. Filing that as a bug wouldn't change the fact that there is no way to address the issue.

Gravatar for achmedrauff.abdulrahim@3ds.com

Comment by Achmed Rauff, Apr 9, 2015 2:25 AM

I somehow resolved the issue for Chrome by using the default skin. It sill does not work on Firefox.

Gravatar for slangevin@coveo.com

Comment by Simon, Apr 9, 2015 9:32 AM

I will sound repetitive but the explanation on the limitation and the workaround is detailed here:

http://source.coveo.com/2015/03/25/browserVSDIP/

Ask a question