When the user exits a FlashCONNECT application, something must be displayed to the browser that allows them to continue. There are two options.
The programmer can program in an ending page, but this requires embedding within the program some knowledge about how the Web site is set up.
Include the w3ClosingPage variable in the URL that called the application in the first place. This way, when the application exits, FlashCONNECT bounces the browser to that URL with the "Location: " command.
The macro "!url" sets w3ClosingPage to the same URL that started the application. This is especially useful for authenticated applications. Setting w3ClosingPage to !url in the URL that starts your application forces the log on screen to display after the user exits your application. Alternatively, w3ClosingPage can be set to a specific URL.
However, an interesting effect takes place when w3ClosingPage is set to the URL which started the application, and profiling, which performs an automatic log on, is turned on. The combination of the two results in the appearance that the user cannot log off. This is because after logging off the application, the application returns to the log on banner (due to w3ClosingPage being set to !url and due to the use of profiling, the user is automatically logged back on again.
When an application starts, the value of w3ClosingPage as defined by the Web page is set in the w3ClosingPage variable defined in w3Input. This variable can be changed by the application.
If the value of w3ClosingPage is obtained via a call to w3GetCGI, then the value of w3ClosingPage as set on the Web form is returned. If the value of w3ClosingPage is used from named common as defined in w3Include, then the current value reflecting application changes is available.
http://www.yourbox.com/cgi-bin/fccgi.exe?w3exec=MyApp?w3ClosingPage=http://www.yourbox.com
http://www.yourbox.com/cgi-bin/fccgi.exe?w3exec=MyAuthApp?w3ClosingPage=!url