MSIR.0801 READ SCREEN encountered in NOSCREEN mode: Difference between revisions
Jump to navigation
Jump to search
(Automatically generated page update) |
(Automatically generated page update) |
||
| Line 1: | Line 1: | ||
A ''[[Janus Web Server]]'' port was defined with the <tt>NOSCREEN</tt> parameter, presumably to prevent accidental entry to Janus Web Legacy mode, but the application running on the port issued a <tt>READ SCREEN</tt>. Either the NOSCREEN setting is working as expected and has caught an accidental <tt>READ SCREEN</tt> or there is a real need to use Janus Web Legacy support on the port. In the former case, correct the application to prevent a <tt>READ SCREEN</tt> from a web request — the <tt>$web</tt> function makes it easy to detect when code is running on a web thread. In the latter case, either remove the <tt>NOSCREEN</tt> parameter from the port definition or add a <tt>SCREEN</tt> parameter to the JANUS WEB ON rule for the URLs which need to use Janus Web Legacy support. | A ''[[Janus Web Server]]'' port was defined with the <tt>NOSCREEN</tt> parameter, presumably to prevent accidental entry to Janus Web Legacy mode, but the application running on the port issued a <tt>READ SCREEN</tt>. Either the NOSCREEN setting is working as expected and has caught an accidental <tt>READ SCREEN</tt> or there is a real need to use Janus Web Legacy support on the port. In the former case, correct the application to prevent a <tt>READ SCREEN</tt> from a web request — the <tt>$web</tt> function makes it easy to detect when code is running on a web thread. In the latter case, either remove the <tt>NOSCREEN</tt> parameter from the port definition or add a <tt>SCREEN</tt> parameter to the JANUS WEB ON rule for the URLs which need to use Janus Web Legacy support. | ||
[[Category:Sirius Mods messages]] | [[Category:Sirius Mods messages]] [[Category:MSIR.0800 - MSIR.0999]] | ||
Revision as of 16:06, 13 August 2015
A Janus Web Server port was defined with the NOSCREEN parameter, presumably to prevent accidental entry to Janus Web Legacy mode, but the application running on the port issued a READ SCREEN. Either the NOSCREEN setting is working as expected and has caught an accidental READ SCREEN or there is a real need to use Janus Web Legacy support on the port. In the former case, correct the application to prevent a READ SCREEN from a web request — the $web function makes it easy to detect when code is running on a web thread. In the latter case, either remove the NOSCREEN parameter from the port definition or add a SCREEN parameter to the JANUS WEB ON rule for the URLs which need to use Janus Web Legacy support.