Difference between revisions of "Regular expression support"
From WPKG | Open Source Software Deployment and Distribution
m |
m |
||
| Line 29: | Line 29: | ||
Normally, hosts are parsed from top to the bottom, except when the hostname is not a regular expression. | Normally, hosts are parsed from top to the bottom, except when the hostname is not a regular expression. | ||
So host "bronek" will match "profile1", even though it also matches "b.+" and "bron.+" (which are regular expressions). | So host "bronek" will match "profile1", even though it also matches "b.+" and "bron.+" (which are regular expressions). | ||
| + | |||
| + | |||
| + | [[category:Documentation]] | ||
Revision as of 19:55, 7 March 2006
WPKG has regular expression support for hosts defined in hosts.xml file.
You can view the exact syntax on this page:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/jscript7/html/jsjsgrpregexpsyntax.asp
Quick examples:
<host name="b[0-9]+" profile-id="profile" />
works for: b1, b10, b100 does not work for: bubu, b, x, x1, x10, x100
<host name=".+" profile-id="profile" />
works for *all* hosts - use with care (!), place at the bottom of hosts.xml
<host name="b.+" profile-id="profile1" />
works for "b10", "b11", "b12345" etc.
<host name="b.+" profile-id="profile2" />
<host name="bronek1" profile-id="profile1" />
<host name="bron.+" profile-id="profile3" />
Normally, hosts are parsed from top to the bottom, except when the hostname is not a regular expression. So host "bronek" will match "profile1", even though it also matches "b.+" and "bron.+" (which are regular expressions).