JANUS WEB ON - Revision history

Tom: /* Named parameters */

2019-09-04T21:02:14Z

Named parameters

← Older revision		Revision as of 21:02, 4 September 2019
Line 375:		Line 375:

	This parameter indicates that the sent document should be scanned for "Server Side Include" tags.		This parameter indicates that the sent document should be scanned for "Server Side Include" tags.

			===WEBSOCKET \| NOWEBSOCKET===

			This parameter overrides the default or explicit JANUS DEFINE setting of the WEBSOCKET/NOWEBSOCKET parameter.

	===WRAPJS===		===WRAPJS===

Dme: /* RAWINPUTONLY | NOTRAWINPUTONLY */

2018-01-20T13:40:15Z

RAWINPUTONLY | NOTRAWINPUTONLY

← Older revision		Revision as of 13:40, 20 January 2018
Line 291:		Line 291:
	If the RAWINPUTONLY parameter is in effect for a URL, the form fields are no longer available with the $Web_form and $Web_Parm functions (that is, the multiple functions whose names begin with these characters), though the $Web_parm, $Web_isindex, and $Web_URL_Parm functions can still be used to access URL parameters.		If the RAWINPUTONLY parameter is in effect for a URL, the form fields are no longer available with the $Web_form and $Web_Parm functions (that is, the multiple functions whose names begin with these characters), though the $Web_parm, $Web_isindex, and $Web_URL_Parm functions can still be used to access URL parameters.

	When using RAWINPUTONLY, the only way to process the form parameters is by retrieving them into a longstring using the [[$Web_Input_Content]] function~~. .el~~ method. To separate the various parameters, this longstring must then be parsed and (usually) URL decoded. If the POST used the default form data encoding of <tt>.application/x-www-form-urlencoded</tt>, each parameter/value pair is separated with an ampersand (&amp.). Processing is considerably more complicated if the encoding is <tt>.multipart/form-data</tt>.		When using RAWINPUTONLY, the only way to process the form parameters is by retrieving them into a longstring using the [[$Web_Input_Content]] function method. To separate the various parameters, this longstring must then be parsed and (usually) URL decoded. If the POST used the default form data encoding of <tt>.application/x-www-form-urlencoded</tt>, each parameter/value pair is separated with an ampersand (&amp.). Processing is considerably more complicated if the encoding is <tt>.multipart/form-data</tt>.

JAL: add word

2016-09-16T19:11:30Z

add word

← Older revision		Revision as of 19:11, 16 September 2016
Line 72:		Line 72:
	The URL <code>/test3</code> would result in the file <code>TEST</code> being opened and the commands <code>I A3</code>, <code>I B3</code> and, <code>.I C3</code> being issued.</li>		The URL <code>/test3</code> would result in the file <code>TEST</code> being opened and the commands <code>I A3</code>, <code>I B3</code> and, <code>.I C3</code> being issued.</li>

	<li>Under Model 204 7.7 and later, an <code>"M</code> in the command is replaced with the name of the method (GET, POST, PUT, etc.) that the client requested. So if a rule had:		<li>Under Model 204 7.7 and later, an <code>"M</code> in the command is replaced with the name of the HTTP method (GET, POST, PUT, etc.) that the client requested. So if a rule had:

	<p class="code">JANUS WEB WEBPORT ON /TEST/* OPEN FILE TEST CMD 'I "M.*'		<p class="code">JANUS WEB WEBPORT ON /TEST/* OPEN FILE TEST CMD 'I "M.*'

JAL: one word change

2016-08-05T16:33:53Z

one word change

← Older revision		Revision as of 16:33, 5 August 2016
Line 72:		Line 72:
	The URL <code>/test3</code> would result in the file <code>TEST</code> being opened and the commands <code>I A3</code>, <code>I B3</code> and, <code>.I C3</code> being issued.</li>		The URL <code>/test3</code> would result in the file <code>TEST</code> being opened and the commands <code>I A3</code>, <code>I B3</code> and, <code>.I C3</code> being issued.</li>

	<li>Under Model 204 7.7 and later, ~~the~~ <code>"M</code> in the command is replaced with the name of the method (GET, POST, PUT, etc.) that the client requested. So if a rule had:		<li>Under Model 204 7.7 and later, an <code>"M</code> in the command is replaced with the name of the method (GET, POST, PUT, etc.) that the client requested. So if a rule had:

	<p class="code">JANUS WEB WEBPORT ON /TEST/* OPEN FILE TEST CMD 'I "M.*'		<p class="code">JANUS WEB WEBPORT ON /TEST/* OPEN FILE TEST CMD 'I "M.*'

ELowell at 16:18, 5 August 2016

2016-08-05T16:18:01Z

Alex: /* CMD cmd [AND cmd [AND...]] */

2016-08-05T04:39:30Z

CMD cmd [AND cmd [AND...]]

← Older revision		Revision as of 04:39, 5 August 2016
Line 64:		Line 64:

	The URL <code>/test3</code> would result in the file <code>TEST</code> being opened and the commands <code>I A3</code>, <code>I B3</code> and, <code>.I C3</code> being issued.		The URL <code>/test3</code> would result in the file <code>TEST</code> being opened and the commands <code>I A3</code>, <code>I B3</code> and, <code>.I C3</code> being issued.

			Under Model 204 7.7 and later, the <code>"M</code> in the command is replaced with the name of the method (GET, POST, PUT, etc.) that the client requested. So if a rule had:

			<p class="code">JANUS WEB WEBPORT ON /TEST/* OPEN FILE TEST CMD 'I "M.*'
			</p>

			A GET request for URL <code>/test/foo</code> would result in the file <code>TEST</code> being opened and the command <code>I GET.FOO</code> being issued. A POST for the same URL ould result in the command <code>I POST.FOO</code> being issued.

	The default procedure file or group at the time the first <var class="term">cmd</var> is executed will be either that specified in the <var>OPEN</var> clause of the <var>JANUS WEB ON</var> command or, if that is not present, the default file or group resulting from the port definition. The default procedure file or group at the time of subsequent <var class="term">cmd</var> executions is whatever happens to be the default after the execution of the preceding <var class="term">cmd</var>.		The default procedure file or group at the time the first <var class="term">cmd</var> is executed will be either that specified in the <var>OPEN</var> clause of the <var>JANUS WEB ON</var> command or, if that is not present, the default file or group resulting from the port definition. The default procedure file or group at the time of subsequent <var class="term">cmd</var> executions is whatever happens to be the default after the execution of the preceding <var class="term">cmd</var>.

JAL: remove displaytitle

2016-01-27T19:41:01Z

remove displaytitle

← Older revision		Revision as of 19:41, 27 January 2016
Line 1:		Line 1:
	~~{{DISPLAYTITLE:JANUS WEB ON}}~~
	<span class="pageSubtitle">Assign actions to URLs</span>		<span class="pageSubtitle">Assign actions to URLs</span>

JDamon: closing was missing in two places on the queequeg line

2015-05-18T18:46:44Z

closing </code> was missing in two places on the queequeg line

← Older revision		Revision as of 18:46, 18 May 2015
Line 51:		Line 51:
	</p>		</p>

	The URL <code>/test5/queequeg</code> would result in the file <code>QA5<code> being opened and procedure <code>QUEEQUEG<code> inside <code>QA5</code> being <var>INCLUDE</var>d.		The URL <code>/test5/queequeg</code> would result in the file <code>QA5</code> being opened and procedure <code>QUEEQUEG</code> inside <code>QA5</code> being <var>INCLUDE</var>d.
	Variable data from a URL can be substituted out of order by indicating the wildcard match position after a double-quote character. For example, given this rule:		Variable data from a URL can be substituted out of order by indicating the wildcard match position after a double-quote character. For example, given this rule:

JAL: /* See also */

2013-08-14T19:01:53Z

JAL: /* CMD cmd [AND cmd [AND...]] */

2013-08-14T18:09:37Z

CMD cmd [AND cmd [AND...]]

← Older revision		Revision as of 18:09, 14 August 2013
Line 33:		Line 33:

	<div id="cmd"></div>		<div id="cmd"></div>
			==Named parameters==
	===CMD cmd [AND cmd [AND...]]===		===CMD cmd [AND cmd [AND...]]===

← Older revision		Revision as of 19:01, 14 August 2013
Line 379:		Line 379:
	<li>[[List of Janus commands]]		<li>[[List of Janus commands]]
	<li>[[List of JANUS WEB subcommands]]		<li>[[List of JANUS WEB subcommands]]
	<li>[[Defining Web rules~~\|"Defining Web rules"~~]]		<li>[[Defining Web rules]]
	</ul>		</ul>

	[[Category:JANUS WEB subcommands\|JANUS WEB ON]]		[[Category:JANUS WEB subcommands\|JANUS WEB ON]]

← Older revision		Revision as of 16:18, 5 August 2016
Line 37:		Line 37:
	This parameter indicates that <var class="term">cmd</var> is to be issued as a <var class="product">Model 204</var> command just as if it had been entered by a user. Multiple commands can be specified by separating the commands with the "AND" keyword.		This parameter indicates that <var class="term">cmd</var> is to be issued as a <var class="product">Model 204</var> command just as if it had been entered by a user. Multiple commands can be specified by separating the commands with the "AND" keyword.

	Each <var class="term">cmd</var> can contain wildcards just as for <var class="term">url</var>. The wildcard characters in <var class="term">cmd</var> are replaced by the incoming request characters that match the corresponding wildcard characters in <var class="term">url</var>. For example~~, if~~ <var class="term">url</var> is <code>/SUBSYS/</code>, <var class="term">cmd</var> is <code></code>, and a request for URL <code>./SUBSYS/SUBSYSMGMT</code> is received, the command <var>SUBSYSMGMT</var> is executed — most likely resulting in the subsystem <var>SUBSYSMGMT</var> being invoked.		<p>Each <var class="term">cmd</var> can contain wildcards just as for <var class="term">url</var>. The wildcard characters in <var class="term">cmd</var> are replaced by the incoming request characters that match the corresponding wildcard characters in <var class="term">url</var>.</p>
			<p>For example:</p>
			<ul>
			<li>If <var class="term">url</var> is <code>/SUBSYS/</code>, <var class="term">cmd</var> is <code></code>, and a request for URL <code>./SUBSYS/SUBSYSMGMT</code> is received, the command <var>SUBSYSMGMT</var> is executed — most likely resulting in the subsystem <var>SUBSYSMGMT</var> being invoked.</li>

	If <var class="term">url</var> is <code>/INCLUDE/TEST/</code>, <var class="term">cmd</var> is <code>INCLUDE WEB.TEST.</code>, and a request for URL <code>TEST/DISPLAY</code> is received, the command INCLUDE WEB.TEST.DISPLAY is executed.		<li>If <var class="term">url</var> is <code>/INCLUDE/TEST/</code>, <var class="term">cmd</var> is <code>INCLUDE WEB.TEST.</code>, and a request for URL <code>TEST/DISPLAY</code> is received, the command INCLUDE WEB.TEST.DISPLAY is executed.</li>

	If <var class="term">url</var> is <code>/INCLUDE//</code>, the <var>CMD</var> clause contains <code>.'INCLUDE ' AND 'INCLUDE '</code>, and a request for the URL <code>.TEST/DISPLAY</code> is received, the commands <var>INCLUDE TEST</var> and <var>INCLUDE DISPLAY</var> are executed.		<li>If <var class="term">url</var> is <code>/INCLUDE//</code>, the <var>CMD</var> clause contains <code>.'INCLUDE ' AND 'INCLUDE '</code>, and a request for the URL <code>.TEST/DISPLAY</code> is received, the commands <var>INCLUDE TEST</var> and <var>INCLUDE DISPLAY</var> are executed.</li>
			</ul>

	Note ~~that unless~~ <var class="term">cmd</var> consists of a single word, it must be enclosed in single quotes.		<p class="note"><b>Note:</b> Unless <var class="term">cmd</var> consists of a single word, it must be enclosed in single quotes.</p>

			<ul>
			<li>
	Wildcard substitution is also performed on files or groups listed in the <var>OPEN</var> clause ([[JANUS WEB ON]]). For example, given this rule:		Wildcard substitution is also performed on files or groups listed in the <var>OPEN</var> clause ([[JANUS WEB ON]]). For example, given this rule:

Line 50:		Line 56:
	</p>		</p>

	The URL <code>/test5/queequeg</code> would result in the file <code>QA5</code> being opened and procedure <code>QUEEQUEG</code> inside <code>QA5</code> being <var>INCLUDE</var>d.		The URL <code>/test5/queequeg</code> would result in the file <code>QA5</code> being opened and procedure <code>QUEEQUEG</code> inside <code>QA5</code> being <var>INCLUDE</var>d. </li>
	Variable data from a URL can be substituted out of order by indicating the wildcard match position after a double-quote character. For example, given this rule:
			<li>Variable data from a URL can be substituted out of order by indicating the wildcard match position after a double-quote character. For example, given this rule:

	<p class="code">JANUS WEB WEBPORT ON //TEST?/ OPEN FILE TEST CMD 'I MOBY"2,*'		<p class="code">JANUS WEB WEBPORT ON //TEST?/ OPEN FILE TEST CMD 'I MOBY"2,*'
	</p>		</p>

	The URL <code>/xyz/test5/tashtego</code> would result in the file <code>TEST</code> being opened and the command <code>I MOBY5,TASHTEGO</code> being issued. As this example illustrates, an asterisk (<tt>*</tt>} after a positional replacement string uses the replacment string after the positional string.		The URL <code>/xyz/test5/tashtego</code> would result in the file <code>TEST</code> being opened and the command <code>I MOBY5,TASHTEGO</code> being issued. As this example illustrates, an asterisk (<tt>*</tt>} after a positional replacement string uses the replacment string after the positional string.</li>

	It is possible with positional replacement strings to re-use replacement strings. For example, given this rule:		<li>It is possible with positional replacement strings to re-use replacement strings. For example, given this rule:

	<p class="code">JANUS WEB WEBPORT ON /TEST* OPEN FILE TEST CMD 'I A"1' AND 'I B"1' and 'I C"1'		<p class="code">JANUS WEB WEBPORT ON /TEST* OPEN FILE TEST CMD 'I A"1' AND 'I B"1' and 'I C"1'
	</p>		</p>

	The URL <code>/test3</code> would result in the file <code>TEST</code> being opened and the commands <code>I A3</code>, <code>I B3</code> and, <code>.I C3</code> being issued.		The URL <code>/test3</code> would result in the file <code>TEST</code> being opened and the commands <code>I A3</code>, <code>I B3</code> and, <code>.I C3</code> being issued.</li>

	Under Model 204 7.7 and later, the <code>"M</code> in the command is replaced with the name of the method (GET, POST, PUT, etc.) that the client requested. So if a rule had:		<li>Under Model 204 7.7 and later, the <code>"M</code> in the command is replaced with the name of the method (GET, POST, PUT, etc.) that the client requested. So if a rule had:

	<p class="code">JANUS WEB WEBPORT ON /TEST/* OPEN FILE TEST CMD 'I "M.*'		<p class="code">JANUS WEB WEBPORT ON /TEST/* OPEN FILE TEST CMD 'I "M.*'
	</p>		</p>

	A GET request for URL <code>/test/foo</code> would result in the file <code>TEST</code> being opened and the command <code>I GET.FOO</code> being issued. A POST for the same URL ~~ould~~ result in the command <code>I POST.FOO</code> being issued.		A GET request for URL <code>/test/foo</code> would result in the file <code>TEST</code> being opened and the command <code>I GET.FOO</code> being issued. A POST for the same URL would result in the command <code>I POST.FOO</code> being issued.</li>
			</ul>

	The default procedure file or group at the time the first <var class="term">cmd</var> is executed will be either that specified in the <var>OPEN</var> clause of the <var>JANUS WEB ON</var> command or, if that is not present, the default file or group resulting from the port definition. The default procedure file or group at the time of subsequent <var class="term">cmd</var> executions is whatever happens to be the default after the execution of the preceding <var class="term">cmd</var>.		The default procedure file or group at the time the first <var class="term">cmd</var> is executed will be either that specified in the <var>OPEN</var> clause of the <var>JANUS WEB ON</var> command or, if that is not present, the default file or group resulting from the port definition. The default procedure file or group at the time of subsequent <var class="term">cmd</var> executions is whatever happens to be the default after the execution of the preceding <var class="term">cmd</var>.