WebSpeed
Developer’s Guide


Debugging and Administrative Options

This section, which appears at the bottom of the debug output, provides you with an interface to all the known debugging options, allowing you to turn them on or off. You can also implement your own application-specific debugging options by adding them to the Current debug options fill-in field or specifying them in the URL. The listings described in this section are supported by install-path/src/web/support/prinval.p.

The value displayed after Debugging Cookie WSDebug is the current value of the Cookie. Due to the way Cookies work, this value always lags behind the value displayed by the Current debug options fill-in, by one request.

To synchronize the Cookie with the debug options, change the debugging options as desired and click the appropriate button to set them. This sets the WSDebug Cookie appropriately. Then click the Reload submit button on the form (not your browser) to reload the page. The values for Current debug options and WSDebug Cookie are then identical. You can then scroll the page back to the top and run your application as usual. Whatever debugging options you set remain active until explicitly changed. However, these debugging settings are set specific to the URL of your application. The WSDebug Cookie is set with the path based on the value of the AppURL variable (see the "Miscellaneous Variables" section for more information about AppURL). This causes the browser to only send the Cookie when visiting any URL that starts with the same leading path.

If your browser does not support Persistent State Cookies, then the value of the WSDebug Cookie remains blank.

Some other options are:

You can also specify multiple debugging options in the URL. Any of the options listed above can be combined. For example, to test the state-aware features, you might specify:

http://webserver/cgi-bin/webapp.cgi/webapp.w?debug=agent,cookies,http 

This returns the output from a file named webapp.w followed by the specified debugging sections. If you want the Debugging and Administration form, the admin option must be specified explicitly unless the generic options “on” or “all” are used. You can also specify this list in the Current debug options fill-in field of the Debugging and Administrative Options form.

Turning off debugging is similar to turning it on. Click the “off” link on the Debugging and Administrative Options form or specify debug=off as an argument in the URL. Then click your browser Reload button.

Agent Specific Information

This section contains information specific to the Agent process that handled the request.

Persistent State Cookies

This section contains a list of all the cookie names received by the browser and the value of each one.

HTTP Headers Sent

This section lists all HTTP headers sent to the browser (for example, Set-Cookie: and Content-Type:). This section will be displayed only if the http option is specified in the URL or on the Administration form.

Miscellaneous Variables

This section contains variables used internally by the WebSpeed Transaction Server, which you can also use in your WebSpeed applications. The SelfURL is always the URL of the current page (minus any arguments), and AppURL is the URL of your application. These variables are derived from the SCRIPT_NAME and PATH_INFO environment variables (see the "Environment Variables" section).

Environment Variables

This section contains all of the environment variables passed to the Messenger process from the Web server. Many of these variables are inherited by the Web server when it is started. Other variables change from request to request.

Form Fields

This section contains fields listed in raw unparsed form and in parsed form that are returned by the get-field( ) API function. This section only contains values if the request is the result of form input or if any arguments are specified following a "?" in the URL.


Copyright © 2004 Progress Software Corporation
www.progress.com
Voice: (781) 280-4000
Fax: (781) 280-4095