Up
appname.conf
fglcl.conf

 

fglcl.conf

Use the fglcl.conf file to configure the HTML Client.

Location

A multiple entry file, like an .ini file would allow the HTML client (fglcl) to find its required information.

For example:

sample.fglserver=198.2.1.0:0
computer.fglserver=198.2.1.0:1

Calls would then be done through fglcl?sample or fglcl?computer.

The full URL could then look like the following:

http://web_server_ip_address/web_server_cgi_alias/fglcl?appName

On Windows NT, you should not place the fglcl.conf file in the registry because spawned cgi binaries might not have access to the Registry. Also, an unknown user could by means of a program read the registry.

The best portable solution is to place the file HTML client (fglcl) program in the CGI binaries directory. This is done for the following reasons:

Some web servers have a WWW_ROOT like the FTP_ROOT for FTP servers and spawned processes cannot access files and directories that are at a higher directory level than WWW_ROOT.
Accessing this file through a web browser will make the system execute rather than read this file (all files in the CGI directory are considered executable).

Syntax

The full syntax for fglcl.conf is:

appName.fglserver={app_server_ip_address}:{port - 6500}
[appName.debug={0|debug_level}]
[appName.HTMLdebug={0|1}]

fglserver
This variable uses the same configuration as the FGLSERVER variable. It must be written fglserver (lowercase). The port number must be specified and is always -6500.
For example, if you plan to run on your machine "app_server" whose IP address is 198.100.150.4, on port 6542, the variable entry would be: fglserver=198.100.150.4:42
debug
This variable indicates debug level. Those debug traces are seen on the standard error (stderr) and will thus not be seen in the HTML page.
Debugging can degrade performance.
HTMLdebug
This flag should be set to 0 (no debugging) or to 1 (debugging).
A setting of 1 will show some debug traces of the client (fglcl) in the browser.

Security

Apache Web Server

Trying to access the fglcl.conf file though the web server will generate the following error:

Forbidden

You do not have permission to access /cgi-bin/fglcl.conf on this server.

Microsoft IIS / Personal Web Server 4.0

When you use the normal configuration with the fglcl.conf file in the CGI binaries directory on IIS / PWS 4.0, the browser displays the following prompt:

There are two considerations regarding fglcl.conf and security on Windows NT :

fglcl.conf is an HTML file and its access should be restricted through the web server.
fglcl.conf is a system file and it should be protected (or secured) as a normal system file.

Security Through the Web Server

You can set security for the file fglcl.conf by launching Microsoft Management Console. Find fglcl.conf in the file list and look at the file's properties. You will see the following dialog box:

fglcl.conf properties

On the File tab, uncheck Read:

fglcl.conf configuration

You can also go the File Security tab and click Edit to change the "Anonymous Access and Authentication Control" configuration.

File Security

In the Authentication Methods dialog box that appears, you can disable everything:

Authentication Methods

Security Through the File System

Make sure that the spawned process (fglcl.exe) can read the fglcl.conf file with the rights from the standard internet guest user. Spawned processes from the web server will be under this user's rights. To specify file permissions, right-click on the file fglcl.conf. Select Properties, and then select the Security tab. Click Permissions to display the File Permissions dialog box.

Summary

When everything is set properly, you will be prompted for a password when trying to access this file from another station.

Internet Explorer and IIS / Personal Web Server have special features that allow them to send and receive data more securely and thus will let the current user on the web server access (read) the fglcl.conf file without any problems. This will not work with the Navigator / IIS pair.

Calling Convention

Enter the following URL in your browser:

http://web_server_ip_address/web_server_cgi_alias/fglcl.exe?appName

For example:

http://www.mycompany.com/cgi-bin/fglcl.exe?application