LEGJS and NOLEGJS (JANUS DEFINE parameters): Difference between revisions
mNo edit summary |
(Automatically generated page update) |
||
| Line 1: | Line 1: | ||
{{DISPLAYTITLE:LEGJS and NOLEGJS}} | {{DISPLAYTITLE:LEGJS and NOLEGJS}} | ||
<span class="pageSubtitle" | <span class="pageSubtitle">Enable/Disable use of Javascript in Janus Legacy application</span> | ||
<var>LEGJS</var> and <var>NOLEGJS</var> are parameters on <var>[[JANUS DEFINE]]</var>, whichs define and sets characteristics of a Janus port. | <var>LEGJS</var> and <var>NOLEGJS</var> are parameters on <var>[[JANUS DEFINE]]</var>, whichs define and sets characteristics of a Janus port. | ||
Latest revision as of 22:17, 16 April 2013
Enable/Disable use of Javascript in Janus Legacy application
LEGJS and NOLEGJS are parameters on JANUS DEFINE, whichs define and sets characteristics of a Janus port.
Indicates whether or not Janus Web Legacy Support is to use JavaScript in the HTML it sends to browsers. The default of LEGJS means that Janus Web Legacy Support will use JavaScript in its generated HTML.
While almost all browsers correctly support the simple JavaScript used by Janus Web Legacy Supportt, and this JavaScript makes the pages generated by Janus Web Legacy Support considerably more "friendly", the NOLEGJS parameter can be specified if a site has rules against the use of JavaScript or if the JavaScript causes problems with some browsers.
The LEGJS and NOLEGJS parameter on the JANUS DEFINE can be overridden on a URL basis by the like-named parameters on JANUS WEB SCREEN rules, and they can be overridden on an application level by the like-named parameters in $Web_Screen calls.
Valid only for WEBSERV ports.