SCREEN and NOSCREEN (JANUS DEFINE parameters): Difference between revisions
mNo edit summary |
mNo edit summary |
||
| Line 4: | Line 4: | ||
<var>SCREEN</var> and <var>NOSCREEN</var> are parameters on [[JANUS DEFINE]], whichs define and sets characteristics of a Janus port. | <var>SCREEN</var> and <var>NOSCREEN</var> are parameters on [[JANUS DEFINE]], whichs define and sets characteristics of a Janus port. | ||
Indicates whether or not <var class="product">[[Janus Web Legacy Support|Janus Web Legacy]]</var> screens will be allowed to appear on requests to the port. <var>SCREEN</var>, the default, specifies that <var class="product">Janus Web Legacy Support</var> automatically renders any 3270 screen presented by an application as part of a <var class="product">Janus Web Legacy</var> session. While this is convenient, it might be viewed as a security risk — 3270 screens not intended for web user consumption might accidentally appear on a browser because of an application error. To avoid this risk, specifying <var>NOSCREEN</var> on the port definition ensures that an attempt to display a 3270 screen on a web request will result in a user restart. | Indicates whether or not <var class="product">[[Janus Web Legacy Support|Janus Web Legacy]]</var> screens will be allowed to appear on requests to the port. <var>SCREEN</var>, the default, specifies that <var class="product">Janus Web Legacy Support</var> automatically renders any 3270 screen presented by an application as part of a <var class="product">Janus Web Legacy</var> session. While this is convenient, it might be viewed as a security risk &mdash; 3270 screens not intended for web user consumption might accidentally appear on a browser because of an application error. To avoid this risk, specifying <var>NOSCREEN</var> on the port definition ensures that an attempt to display a 3270 screen on a web request will result in a user restart. | ||
The <var>SCREEN</var> and <var>NOSCREEN</var> parameters are available in | The <var>SCREEN</var> and <var>NOSCREEN</var> parameters are available in <var class="product">Sirius Mods</var> Version 6.3 and later. | ||
You can override the <var>SCREEN</var> and <var>NOSCREEN</var> parameters on the <var>JANUS DEFINE</var> command on a URL basis using the like-named parameters in JANUS WEB ON rules. | You can override the <var>SCREEN</var> and <var>NOSCREEN</var> parameters on the <var>JANUS DEFINE</var> command on a URL basis using the like-named parameters in JANUS WEB ON rules. | ||
Revision as of 20:19, 2 March 2012
<section begin="desc" />Allow/Disallow legacy screens<section end="desc" />
SCREEN and NOSCREEN are parameters on JANUS DEFINE, whichs define and sets characteristics of a Janus port.
Indicates whether or not Janus Web Legacy screens will be allowed to appear on requests to the port. SCREEN, the default, specifies that Janus Web Legacy Support automatically renders any 3270 screen presented by an application as part of a Janus Web Legacy session. While this is convenient, it might be viewed as a security risk — 3270 screens not intended for web user consumption might accidentally appear on a browser because of an application error. To avoid this risk, specifying NOSCREEN on the port definition ensures that an attempt to display a 3270 screen on a web request will result in a user restart.
The SCREEN and NOSCREEN parameters are available in Sirius Mods Version 6.3 and later.
You can override the SCREEN and NOSCREEN parameters on the JANUS DEFINE command on a URL basis using the like-named parameters in JANUS WEB ON rules.
Valid only for WEBSERV ports.