This appendix presents a description of the generic page and service tagging conventions supported for use with RUEI.
Note that tags are matched in the order in which they appear in Table A-1. That is, the highest rows take priority over the lower rows. See the section below for information about matching schemes.
Tag | Scheme | StructureFoot 1 |
---|---|---|
C C |
|
|
C C C C C |
|
|
custom function (TAGNAME is function name) |
C C |
|
(TAGNAME is name) |
C C C |
|
C C C C |
|
|
C C |
|
|
C C |
|
|
C C |
|
|
OracleFoot 2 |
C C C C A A |
|
C C |
|
|
C C C C |
|
|
C C |
|
|
C C* |
|
|
XiTiFoot 3 |
C C |
|
Footnote 1 * is zero (or more) characters of any kind. % is the matching part of the string.
Footnote 2 Contains the deprecated Moniforce tagging. Note this does not automatically work for all Oracle products.
Footnote 3 In addition to the pipe (|) character, "::" can also be specified as a page group separator.
For all page-tagging schemes listed in Table A-1, the pipe character (|) can be specified within a tag as a page-group separator.
C is matching in content (* is optional).
A is matching an argument in a URL.
% is the matching part of the string.
[...]* indicates zero or more occurrences.
[...]+ indicates one or more occurrences.
[^...]* indicates zero or more exclusive (not) occurrences.
\t indicates a tab character.
Note:
Tag matching is case insensitive.Service tags are matched as shown in Table A-2.
Table A-2 Service Tag Matching
Tag | Scheme | Description |
---|---|---|
H |
Matches the following supported HTTP methods: ACL, CONNECTFoot 1 , COPY, DELETE, GETFootref 1, LOCK, MKCOL, MOVE, OPTIONS, PROPFIND, PROPPATCH, PUT, REPORT, SEARCH, TRACE, and UNLOCK. |
Footnote 1 By default, RUEI supports all GET, POST, and CONNECT methods.