Applies to IE Browser publications.
If you use some ActiveX controls, objects or plug-ins in your HTML documents, some of them may not work properly in IE publications. In fact, these plug-ins may require an input file Java applets (CLASS)... In order to read this input file, the plug-in may require that file to be either downloaded from an HTTP server (through an HTTP connection) or read from a physical file on the hard disk; in other words not directly from memory.
| IMPORTANT: the built-in HTTP server will only deliver files which are listed in the Page Dependencies and/or identified as "Special Content" in the Content FileTypes page. |
If you want to enable the built-in HTTP server in your publication, you have to specify a default connection port (generally 8080). If this port is already in use (by another server for instance), the runtime module will try random ports. If no free port is found, an error message is displayed.
Since an HTTP server is created, some users may use any HTTP client (such as a Download Manager or even a simple web browser) to download content from your publication. To avoid this situation, your publication can use encode filenames to deliver files. This operation is transparent and secure. Disabling this option is not recommended.
Finally, to avoid possible cross-domain security problems with the Adobe Flash Player, you can let HTML Executable add a custom crossdomain.xml file.
