SCREEN and NOSCREEN (JANUS DEFINE parameters): Difference between revisions
mNo edit summary |
m (remove "Sirius Mods") |
||
| (7 intermediate revisions by 4 users not shown) | |||
| Line 1: | Line 1: | ||
{{DISPLAYTITLE:SCREEN and NOSCREEN}} | {{DISPLAYTITLE:SCREEN and NOSCREEN}} | ||
<span class="pageSubtitle" | <span class="pageSubtitle">Allow/Disallow legacy screens</span> | ||
<var>SCREEN</var> and <var>NOSCREEN</var> are parameters on [[JANUS DEFINE]], | <var>SCREEN</var> and <var>NOSCREEN</var> are parameters on <var>[[JANUS DEFINE]]</var>, which defines 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 — 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. | ||
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 <var>[[JANUS WEB ON]]</var> 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. | |||
Valid only for <var>[[JANUS DEFINE#type|WEBSERV]]</var> ports. | Valid only for <var>[[JANUS DEFINE#type|WEBSERV]]</var> ports. | ||
Latest revision as of 23:09, 7 June 2016
Allow/Disallow legacy screens
SCREEN and NOSCREEN are parameters on JANUS DEFINE, which defines 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.
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.