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
Miscellaneousvariables 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.
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:
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.
ON — Turn on all of the above
