JANUS WEB rule matching order and examples - Revision history

JAL: remove displaytitle

2016-01-27T18:12:27Z

remove displaytitle

← Older revision		Revision as of 18:12, 27 January 2016
Line 1:		Line 1:
	~~{{DISPLAYTITLE:JANUS WEB Rule matching order and examples}}~~		<span class="pageSubtitle">WEB rule matching order and examples</span>
	<span class="pageSubtitle">WEB ~~Rule~~ matching order and examples</span>

	Each execution of a <var>JANUS WEB</var> command adds to the set of rules for the specified <var>WEBSERV</var> port. Individual rules cannot be deleted nor modified; all rules can be deleted only by stopping and deleting the port definition. However, this should not be necessary, as long as you follow the two golden rules:		Each execution of a <var>JANUS WEB</var> command adds to the set of rules for the specified <var>WEBSERV</var> port. Individual rules cannot be deleted nor modified; all rules can be deleted only by stopping and deleting the port definition. However, this should not be necessary, as long as you follow the two golden rules:

JAL at 20:39, 16 April 2013

2013-04-16T20:39:24Z

JAL: /* References */

2013-04-16T20:27:00Z

References

← Older revision		Revision as of 20:27, 16 April 2013
Line 47:		Line 47:
	In the above example, any request for access to the <tt>/pensions</tt> directory instead causes the <var class="product">Model 204</var> group PENSIONS to open and the routine PENSIONS_DRIVER to be invoked.		In the above example, any request for access to the <tt>/pensions</tt> directory instead causes the <var class="product">Model 204</var> group PENSIONS to open and the routine PENSIONS_DRIVER to be invoked.

	==~~References~~==		==See also==
			<ul>
	~~See:~~ [[List of Janus commands]] ~~and~~ [[List of JANUS WEB subcommands]]		<li>[[List of Janus commands]]
			<li>[[List of JANUS WEB subcommands]]
			</ul>

	[[Category:JANUS WEB subcommands\|JANUS WEB Rule matching order and examples]]		[[Category:JANUS WEB subcommands\|JANUS WEB Rule matching order and examples]]

JALWiccan: Automatically generated page update

2013-04-16T17:32:09Z

Automatically generated page update

← Older revision		Revision as of 17:32, 16 April 2013
Line 1:		Line 1:
	{{DISPLAYTITLE:JANUS WEB Rule matching order and examples}}		{{DISPLAYTITLE:JANUS WEB Rule matching order and examples}}
	<span class="pageSubtitle"~~><section begin="desc" /~~>WEB Rule matching order and examples~~<section end="desc" />~~</span>		<span class="pageSubtitle">WEB Rule matching order and examples</span>

	Each execution of a JANUS WEB command adds to the set of rules for the specified WEBSERV port. Individual rules cannot be deleted nor modified; all rules can be deleted only by stopping and deleting the port definition. However, this should not be necessary, as long as you follow the two golden rules:		Each execution of a JANUS WEB command adds to the set of rules for the specified WEBSERV port. Individual rules cannot be deleted nor modified; all rules can be deleted only by stopping and deleting the port definition. However, this should not be necessary, as long as you follow the two golden rules:

JALWiccan: 1 revision

2012-10-30T01:02:39Z

1 revision

← Older revision	Revision as of 01:02, 30 October 2012
(No difference)

Alex at 01:02, 30 October 2012

2012-10-30T01:02:25Z

← Older revision		Revision as of 01:02, 30 October 2012
Line 36:		Line 36:
	<p class="code">JANUS WEB SIRIUS TYPE .HTML HTML_		<p class="code">JANUS WEB SIRIUS TYPE .HTML HTML_
	</p>		</p>
	The ''[[Janus Web Server]]'' default assumption is that the requested URL is stored in a ''Model 204'' procedure. If the above TYPE rule is in effect and a request comes in for WELCOME.HTML, the server looks in the default procedure file for procedure HTML_WELCOME and returns its contents to the user.		The ''[[Janus Web Server]]'' default assumption is that the requested URL is stored in a <var class="product">Model 204</var> procedure. If the above TYPE rule is in effect and a request comes in for WELCOME.HTML, the server looks in the default procedure file for procedure HTML_WELCOME and returns its contents to the user.

	Virtually any character that is valid in a URL specification is valid as part of a ''Model 204'' procedure name, so the ''[[Janus Web Server]]'' satisfies by default a request for		Virtually any character that is valid in a URL specification is valid as part of a <var class="product">Model 204</var> procedure name, so the ''[[Janus Web Server]]'' satisfies by default a request for
	<nowiki>http://www.x.com:80/staff/bobsmith/welcome.html</nowiki> by sending the contents of the procedure "staff/bobsmith/welcome.HTML" from the default ''Model 204'' file to the client.		<nowiki>http://www.x.com:80/staff/bobsmith/welcome.html</nowiki> by sending the contents of the procedure "staff/bobsmith/welcome.HTML" from the default <var class="product">Model 204</var> file to the client.

	To change this default behavior, you can use an ON rule to cause a request for a specific URL to initiate some other process, as in :		To change this default behavior, you can use an ON rule to cause a request for a specific URL to initiate some other process, as in :
Line 45:		Line 45:
	</p>		</p>

	In the above example, any request for access to the <tt>/pensions</tt> directory instead causes the ''Model 204'' group PENSIONS to open and the routine PENSIONS_DRIVER to be invoked.		In the above example, any request for access to the <tt>/pensions</tt> directory instead causes the <var class="product">Model 204</var> group PENSIONS to open and the routine PENSIONS_DRIVER to be invoked.

	==References==		==References==

Alex at 21:53, 27 December 2011

2011-12-27T21:53:24Z

New page

{{DISPLAYTITLE:JANUS WEB Rule matching order and examples}}
<section begin="desc" />WEB Rule matching order and examples<section end="desc" />

Each execution of a JANUS WEB command adds to the set of rules for the specified WEBSERV port. Individual rules cannot be deleted nor modified; all rules can be deleted only by stopping and deleting the port definition. However, this should not be necessary, as long as you follow the two golden rules:
<ol>

<li>Specify the most general rules first and the most specific last.
<li>Specify a first rule that will "clear" all related rules.
</ol>

The following example illustrates these principles:
JANUS WEB TEST21 DISALLOW *
JANUS WEB TEST21 ALLOW IPADDR 198.242.244.0-24
JANUS WEB TEST21 ALLOW IPADDR 169.84.128.0-3
JANUS WEB TEST21 DISALLOW IPADDR 169.84.128.17
JANUS WEB TEST21 ALLOW USER *


In this example, any previously specified ALLOW rules on port TEST21 are made obsolete by the first DISALLOW rule. Once the TEST21 access rules are cleared, two subnets are given access permission, and then a single specific IP address within one of those subnets has its access revoked. Finally, the <var>ALLOW USER *</var> forces logon processing for all users.

Similar processing takes place for redirection commands. To redirect a specified URL to another URL, use the REDIRECT command:
 JANUS WEB SIRIUS REDIRECT *.jav <nowiki>http://sirius-software.com:8080/java/*.jav</nowiki>


In the example above, requests for Java executables are routed out of the ''[[Janus Web Server]]'' <var>SIRIUS</var> and onto a java directory at port 8080 at <var>sirius-software.com</var>.
A block of redirection commands might look like this:
JANUS WEB SIRIUS NOREDIRECT
JANUS WEB SIRIUS REDIRECT *.jav <nowiki>http://sirius-software.com:8080/java/*.jav</nowiki>
JANUS WEB SIRIUS REDIRECT *.jpg <nowiki>http://sirius-software.com:8001/images/*.jpg</nowiki>


In this example, all previously defined redirection is removed, Java executables are routed out of the ''[[Janus Web Server]]'' <var>SIRIUS</var> and onto a java directory at port 8080 at <var>sirius-software.com</var>, and JPEG images are redirected to an IMAGES directory on port 8001 at
<var>sirius-software.com</var>.

TYPE rules are used to customize processing for certain patterns of incoming URLs. For example
JANUS WEB SIRIUS TYPE *.HTML HTML_*

The ''[[Janus Web Server]]'' default assumption is that the requested URL is stored in a ''Model 204'' procedure. If the above TYPE rule is in effect and a request comes in for WELCOME.HTML, the server looks in the default procedure file for procedure HTML_WELCOME and returns its contents to the user.

Virtually any character that is valid in a URL specification is valid as part of a ''Model 204'' procedure name, so the ''[[Janus Web Server]]'' satisfies by default a request for
<nowiki>http://www.x.com:80/staff/bobsmith/welcome.html</nowiki> by sending the contents of the procedure "staff/bobsmith/welcome.HTML" from the default ''Model 204'' file to the client.

To change this default behavior, you can use an ON rule to cause a request for a specific URL to initiate some other process, as in :
JANUS WEB SIRIUS ON /pensions/* OPEN GROUP PENSIONS CMD 'I PENSIONS_DRIVER'


In the above example, any request for access to the <tt>/pensions</tt> directory instead causes the ''Model 204'' group PENSIONS to open and the routine PENSIONS_DRIVER to be invoked.

==References==

See: [[List of Janus commands]] and [[List of JANUS WEB subcommands]]

[[Category:JANUS WEB subcommands|JANUS WEB Rule matching order and examples]]

Dme: moved JANUS WEB Rule matching order and examples to JANUS WEB rule matching order and examples

2011-10-14T20:30:23Z

moved JANUS WEB Rule matching order and examples to JANUS WEB rule matching order and examples

← Older revision	Revision as of 20:30, 14 October 2011
(No difference)

JALWiccan: 1 revision

2011-07-01T00:13:36Z

1 revision

← Older revision	Revision as of 00:13, 1 July 2011
(No difference)

Admin: 1 revision

2011-07-01T00:13:32Z

1 revision

← Older revision		Revision as of 00:13, 1 July 2011
Line 31:		Line 31:


	In the example above, requests for Java executables are routed out of the ''[[Janus Web Server]]'' <tt>SIRIUS</tt> and onto a java directory at port 8080 at <tt>sirius&hyph.software.com</tt>.		In the example above, requests for Java executables are routed out of the ''[[Janus Web Server]]'' <tt>SIRIUS</tt> and onto a java directory at port 8080 at <tt>sirius&hyph.software.com</tt>.
	A block of redirection commands might look like this:		A block of redirection commands might look like this:
	<p class="code"> JANUS WEB SIRIUS NOREDIRECT		<p class="code"> JANUS WEB SIRIUS NOREDIRECT
Line 41:		Line 41:


	In this example, all previously defined redirection is removed, Java executables are routed out of the ''[[Janus Web Server]]'' <tt>SIRIUS</tt> and onto a java directory at port 8080 at <tt>sirius&hyph.software.com</tt>, and JPEG images are redirected to an IMAGES directory on port 8001 at		In this example, all previously defined redirection is removed, Java executables are routed out of the ''[[Janus Web Server]]'' <tt>SIRIUS</tt> and onto a java directory at port 8080 at <tt>sirius&hyph.software.com</tt>, and JPEG images are redirected to an IMAGES directory on port 8001 at
	<li>.sirius&hyph.software.com</tt>.		<li>.sirius&hyph.software.com</tt>.


Line 68:		Line 68:
	[[Category:JANUS WEB subcommands\|JANUS WEB Rule matching order and examples]]		[[Category:JANUS WEB subcommands\|JANUS WEB Rule matching order and examples]]
	[[Category:Janus commands\|JANUS WEB Rule matching order and examples]]		[[Category:Janus commands\|JANUS WEB Rule matching order and examples]]
	~~[[Category:Sirius commands\|JANUS WEB Rule matching order and examples]]~~

← Older revision		Revision as of 20:39, 16 April 2013
Line 2:		Line 2:
	<span class="pageSubtitle">WEB Rule matching order and examples</span>		<span class="pageSubtitle">WEB Rule matching order and examples</span>

	Each execution of a JANUS WEB command adds to the set of rules for the specified WEBSERV port. Individual rules cannot be deleted nor modified; all rules can be deleted only by stopping and deleting the port definition. However, this should not be necessary, as long as you follow the two golden rules:		Each execution of a <var>JANUS WEB</var> command adds to the set of rules for the specified <var>WEBSERV</var> port. Individual rules cannot be deleted nor modified; all rules can be deleted only by stopping and deleting the port definition. However, this should not be necessary, as long as you follow the two golden rules:
	<ol>		<ol>

Line 17:		Line 17:
	</p>		</p>

	In this example, any previously specified ALLOW rules on port TEST21 are made obsolete by the first DISALLOW rule. Once the TEST21 access rules are cleared, two subnets are given access permission, and then a single specific IP address within one of those subnets has its access revoked. Finally, the <~~var~~>ALLOW USER *</~~var~~> forces logon processing for all users.		In this example, any previously specified ALLOW rules on port <code>TEST21</code> are made obsolete by the first <var>DISALLOW</var> rule. Once the <code>TEST21</code> access rules are cleared, two subnets are given access permission, and then a single specific IP address within one of those subnets has its access revoked. Finally, the <code>ALLOW USER *</code> forces logon processing for all users.

	Similar processing takes place for redirection commands. To redirect a specified URL to another URL, use the REDIRECT command:		Similar processing takes place for redirection commands. To redirect a specified URL to another URL, use the <var>REDIRECT</var> command:
	<p class="code"> JANUS WEB SIRIUS REDIRECT .jav <nowiki>http://sirius-software.com:8080/java/.jav</nowiki>		<p class="code">JANUS WEB SIRIUS REDIRECT .jav <nowiki>http://sirius-software.com:8080/java/.jav</nowiki>
	</p>		</p>

	In the example above, requests for Java executables are routed out of the ''[[Janus Web Server]]'' <~~var~~>SIRIUS</~~var~~> and onto a java directory at port 8080 at <~~var~~>sirius-software.com</~~var~~>.		In the example above, requests for Java executables are routed out of the [[Janus Web Server]] <code>SIRIUS</code> and onto a java directory at port 8080 at <code>sirius-software.com</code>.
	A block of redirection commands might look like this:		A block of redirection commands might look like this:
	<p class="code">JANUS WEB SIRIUS NOREDIRECT		<p class="code">JANUS WEB SIRIUS NOREDIRECT
Line 30:		Line 30:
	</p>		</p>

	In this example, all previously defined redirection is removed, Java executables are routed out of the ~~''[[~~Janus Web Server~~]]''~~ <~~var~~>SIRIUS</~~var~~> and onto a java directory at port 8080 at <~~var~~>sirius-software.com</~~var~~>, and JPEG images are redirected to an IMAGES directory on port 8001 at		In this example, all previously defined redirection is removed, Java executables are routed out of the Janus Web Server <code>SIRIUS</code> and onto a java directory at port 8080 at <code>sirius-software.com</code>, and JPEG images are redirected to an <code>IMAGES</code> directory on port 8001 at
	<~~var~~>sirius-software.com</~~var~~>.		<code>sirius-software.com</code>.

	TYPE rules are used to customize processing for certain patterns of incoming URLs. For example		<var>TYPE</var> rules are used to customize processing for certain patterns of incoming URLs. For example
	<p class="code">JANUS WEB SIRIUS TYPE .HTML HTML_		<p class="code">JANUS WEB SIRIUS TYPE .HTML HTML_
	</p>		</p>
	The ~~''[[~~Janus Web Server~~]]''~~ default assumption is that the requested URL is stored in a <var class="product">Model 204</var> procedure. If the above TYPE rule is in effect and a request comes in for WELCOME.HTML, the server looks in the default procedure file for procedure HTML_WELCOME and returns its contents to the user.		The Janus Web Server default assumption is that the requested URL is stored in a <var class="product">Model 204</var> procedure. If the above <var>TYPE</var> rule is in effect and a request comes in for <code>WELCOME.HTML</code>, the server looks in the default procedure file for procedure <code>HTML_WELCOME</code> and returns its contents to the user.

	Virtually any character that is valid in a URL specification is valid as part of a <var class="product">Model 204</var> procedure name, so the ~~''[[~~Janus Web Server~~]]''~~ satisfies by default a request for		Virtually any character that is valid in a URL specification is valid as part of a <var class="product">Model 204</var> procedure name, so the Janus Web Server satisfies by default a request for
	<nowiki>http://www.x.com:80/staff/bobsmith/welcome.html</nowiki> by sending the contents of the procedure "staff/bobsmith/welcome.HTML" from the default <var class="product">Model 204</var> file to the client.		<code><nowiki>http://www.x.com:80/staff/bobsmith/welcome.html</nowiki></code> by sending the contents of the procedure "staff/bobsmith/welcome.HTML" from the default <var class="product">Model 204</var> file to the client.

	To change this default behavior, you can use an ON rule to cause a request for a specific URL to initiate some other process, as in :		To change this default behavior, you can use an <var>ON</var> rule to cause a request for a specific URL to initiate some other process, as in:
	<p class="code">JANUS WEB SIRIUS ON /pensions/* OPEN GROUP PENSIONS CMD 'I PENSIONS_DRIVER'		<p class="code">JANUS WEB SIRIUS ON /pensions/* OPEN GROUP PENSIONS CMD 'I PENSIONS_DRIVER'
	</p>		</p>

	In the above example, any request for access to the <tt>/pensions</tt> directory instead causes the <var class="product">Model 204</var> group PENSIONS to open and the routine PENSIONS_DRIVER to be invoked.		In the above example, any request for access to the <code>/pensions</code> directory instead causes the <var class="product">Model 204</var> group <code>PENSIONS</code> to open and the routine <code>PENSIONS_DRIVER</code> to be invoked.

	==See also==		==See also==