extensions"
From Documentation
m |
m (correct highlight (via JWB)) |
||
| (One intermediate revision by one other user not shown) | |||
| Line 2: | Line 2: | ||
'''Syntax:''' | '''Syntax:''' | ||
| − | <extensions>''.ext1, .ext2, . | + | <extensions>''.ext1, .ext2, .ext''</extensions> |
[Optional][Default: ''empty''] | [Optional][Default: ''empty''] | ||
| Line 10: | Line 10: | ||
By default, it is ''empty'' which means ZEST handles only URI without any extensions. | By default, it is ''empty'' which means ZEST handles only URI without any extensions. | ||
| − | For example, the following statement indicates ZEST shall handle no extension, < | + | For example, the following statement indicates ZEST shall handle no extension, <code>.do</code> and <code>.action</code>: |
<source lang="xml"> | <source lang="xml"> | ||
Latest revision as of 02:57, 18 January 2022
Syntax:
<extensions>.ext1, .ext2, .ext</extensions>
[Optional][Default: empty]
It specifies a list of extensions that ZEST shall handle. If the extension of a request's URI does match any of them, it will be ignored (and handled as if ZEST is not installed).
By default, it is empty which means ZEST handles only URI without any extensions.
For example, the following statement indicates ZEST shall handle no extension, .do and .action:
<extensions>, .do, .action</extensions>
Notice that, to have better performance, ZEST matches the extension first before searching the action definitions. If you'd like to have an action definition matches a URI with an extension, make sure the extension of the URI is also specified here.
Version History
| Version | Date | Content |
|---|---|---|