These directives controls the "client-side" behaviors of Wapache.
By default ActiveX is enabled in Wapache. If your application does not make use of ActiveX technology, you may choose to turn it off.
Not all ActiveX controls will work properly in Wapache. Those that bypass Windows's Internet service and implement their HTTP own retrieval mechanism will not work.
If an ActiveX control is not already installed, Wapache will prompt the user to install it in a dialog box, just as it happens in Internet Explorer. The
Warning: An ActiveX control installed through Wapache will become available in Internet Explorer as well. Do not create a control that gives you full access to the computer.
This directive specifies the icon that appears at the upper right-hand corner of windows, in the Task Bar, the Task Switch window, and the System Tray. You can assign a specific icon to a window using the
Windows XP: When the Task Bar collapses multiple buttons into a single "program group" button, it obtains the icon and application name from the resource data stored in the executable file. To customize them, you need to use a Win32 resource editor.
Warning: Among the things you can do through the external object is starting a program. Understand the security implicition before turning it on, especially if your application is going to display contents retrieved from the web.
Your application will likely have at least one
The URLs are open in the order as they appear in the configuration file. The first
Tool windows and dialog boxes are positioned relative to their opener, so for them, it's important that the correct opener is specified.
Java is enabled by default. Java applets embedded in HTML pages will only work, however, if the end user had installed the Java Runtime Environment on his/her computer.