Xojo Web app inside FileMaker Webviewer

We compile a very simple web app…Just a “hello world” label on a window…
We compile it as a standalone web app on port 9000…We call that address in a FileMaker 16 or 17 webviewer
First load = OK (load instantly)
Second load = OK (load instantly)

The third time…FM webviewer seems to indicate it is loading…it worked but it take more than 60 seconds to load
Any ideas ?

Work OK on mac…but not in windows…
Build in 2018r4 but we also try older version without success


Make sure the security settings for the web app are set to allow being embedded.


Hello Greg,

I work with Alain… we do all frameoption and nothing seem like resolve our problem

One possibility would be to Run the web app right in Xojo so if it hangs you can press the pause button to see what it is doing.

Please make sure your URL to the web app in FileMaker’s Webviewer starts with http://

Greg : The problem only occur on via FileMaker on windows… If run inside Xojo…it runs OK…as well as on Filemaker Mac.

Christian : we call it via https… i supposed also there is no hsts that force https

Don’t remember it work twice before the problem occur…

It has to be something with xojo…we have other htmlviewer in filemaker that we intensively load, reload javascript…and it work perfectly on windows and mac.

Any ideas ? Problem still there with 2019r1

Did you make an example so that we can have a look at what you did?

Here is a shot in the dark: You may need to add an entry for in the computer’s hosts file. You will need elevated privileges when you start your text editor. Hosts should be located in the system32/drivers/etc folder. On my win10 laptop, the hosts file is empty. Here is an example from another computer:

[code]# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.

This file contains the mappings of IP addresses to host names. Each

entry should be kept on an individual line. The IP address should

be placed in the first column followed by the corresponding host name.

The IP address and the host name should be separated by at least one


Additionally, comments (such as these) may be inserted on individual

lines or following the machine name denoted by a ‘#’ symbol.

For example: rhino.acme.com # source server x.acme.com # x client host

localhost name resolution is handled within DNS itself. localhost

::1 localhost[/code]

You would simply uncomment the localhost line in this example.