Hi,
A client has built a results page using a freemarker template that loads the header content from an external url:
<#ftl encoding="utf-8" />
<#import "/web/templates/modernui/funnelback_classic.ftl" as s/>
<#import "/web/templates/modernui/funnelback.ftl" as fb/>
<!-- start head_index -->
<@fb.IncludeUrl url="https://www.myexamplewebpage.com/search/head_index.html.inc" />
<!-- end head_index -->
The url is reachable from the server (and from anywhere else) but when the page loads, the external content doesn’t display and the following error is shown (when viewing the page’s source):
<!-- start head_index -->
<!-- start head_index -->
<!-- Error while requesting remote content. Please check the logs --><!-- end head_index -->
<!-- end head_index -->
I have tried replacing the url with a generic http page, and that loads with no issues.
The funnelback version is 15.10.0 (45106 #60) - could you please let me know if this is a known issue that has been fixed in later releases?
It could possibly be an issue with Java and the https page that is being requested as I know there have been a number of things that have changed (in terms of supported cyphers and so on) over the last few years. I can’t recall specifically if 15.10 was one of the affected versions but there is a good chance it was affected and would be resolved by upgrading to a newer version.
Check the modernui logs for the collection (from the collection logs section fior the affected collection in the administration interface) - there should be a stack trace in there.
Do you know if the page is available via http - if so try that as well as it could be an easier fix for your problem if it is caused by an unsupported cypher or certificate type.
If you’re still having problems get in touch with your support as well as they can chase this up and give you a definitive answer.
I have discussed this matter with Gioan who advised to post here (I am a Squiz UK CRU member)
I have tried changing the links to http in the freemarker file, but unfortunately the remote server forces redirects to the https version of the page.
That’s the reason why I tested it with a generic http link, which works as expected.
Gioan and I had a look at the modernui logs and couldn’t find anything pointing to the error.
I will update the client with your notes and we’ll see what they come back with.