I apologize in advance for the lack of brevity; this is a very odd query.
I've been using ZoomIndexer for a couple of years with a "website" which is essentially just a file system. My organization has limited resources and due to security concerns, we are limited in our scope.
At any rate, due to these restrictions, we output the index files in Javascript. The searches work effectively enough, but are typically slow given the size of the "site". The effect is amplified for users off-site.
We have recently adopted Sharepoint as a collaboration tool, and I was trying to use this to bridge the gap for our external users. Latency seems to not be a factor for Sharepoint users, at least not nearly as bad using VPN to access the site as it.
The idea is to have the external users jump to the Sharepoint site where the search files live. Then by use of absolute paths in the generated results, jump back to the file system.
However in testing this, attempting to follow the returned links doesn't exit the Sharepoint site; the file path keeps being preceded by http://. The file path is otherwise correct.
When I create a link with an absolute path directly into the HTML search page within Sharepoint, following the link jumps to the linked file outside of Sharepoint as I intended in the first place.
TL;DR: Why do linked search results returned by Javascript report behave in a different manner than other links on the same page?
It's very puzzling. Any help or insight would be greatly appreciated!
I'm also pursuing leads with Sharepoint evangelists.
I've been using ZoomIndexer for a couple of years with a "website" which is essentially just a file system. My organization has limited resources and due to security concerns, we are limited in our scope.
At any rate, due to these restrictions, we output the index files in Javascript. The searches work effectively enough, but are typically slow given the size of the "site". The effect is amplified for users off-site.
We have recently adopted Sharepoint as a collaboration tool, and I was trying to use this to bridge the gap for our external users. Latency seems to not be a factor for Sharepoint users, at least not nearly as bad using VPN to access the site as it.
The idea is to have the external users jump to the Sharepoint site where the search files live. Then by use of absolute paths in the generated results, jump back to the file system.
However in testing this, attempting to follow the returned links doesn't exit the Sharepoint site; the file path keeps being preceded by http://. The file path is otherwise correct.
When I create a link with an absolute path directly into the HTML search page within Sharepoint, following the link jumps to the linked file outside of Sharepoint as I intended in the first place.
TL;DR: Why do linked search results returned by Javascript report behave in a different manner than other links on the same page?
It's very puzzling. Any help or insight would be greatly appreciated!
I'm also pursuing leads with Sharepoint evangelists.
Comment