|
Completing a URIMAP definition for a static response to an HTTP request for XCICS as an HTTP server |
|
|
For a static response, when you have started the URIMAP definition by specifying the components of the expected URL (scheme, host and path) and other basic information, complete the definition by providing the information that XCICS needs to construct the static response to the request, using a resource file. You can use a wildcard for path matching, where XCICS takes the portion of each HTTP request's path that is covered by the wildcard character, and substitutes this as the last part of the file path. When you have planned your static response and started your URIMAP definition, complete the definition following the instructions in this topic. The XCICS System Management Guide contains information about URIMAP resource definition attributes that you will use during this process. Note: When you deliver items as a static response, basic authentication does not operate. Resource level security cannot be applied to these items. If you need to apply access controls based on a user ID to an item delivered in this way, you need to deliver the material as an application-generated response instead.
Example define urimap name=URI1, type=static, usage=server, host="*", path="/home/*", file="$HOME/regtest/web/*";
|