Built-in HTTP Server

Applies to IE Browser publications.

If you use some active objects (HTML5 audio or video player) or plug-ins (Flash…) in your HTML documents, some of them may not work properly in IE publications. In fact, these plug-ins may require an input file. 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.

By default, the built-in server is enabled and it will be activated automatically when files that must be served are requested.

HTML Executable’s built-in server is able to deliver large files and support streaming, which is useful for audio and video files.

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.

You can disable the built-in HTTP server in your publication if you don’t have problematic content type such as audio or video. This can also lower antivirus false positives.

Note: the server requires a default connection port: the runtime module will try random ports. If no free port is found after 3 tries, 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.

Using the built-in HTTP server for Java applets


Copyright G.D.G. Software 2018. All rights reserved