Technical notes
- Multiple URL templates can be mapped to the same object (for example, app_snoop maps to URLs on two different servers).
- Objects can be nested (for example, app_hitcount and app_hitcount/ejb).
- An incoming URL request is compared against templates in order, from top to bottom. When a match is found, processing stops. Therefore, place the more restrictive templates at the top of the file.
- To
activate the definitions in the
dynurl.conffile, issue the dynurl update command (use pdadmin server task).The update occurs immediately and the objects appear in the Web Portal Manager when you refresh the protected object space view.
- Avoid uppercase characters in the object name. Use lowercase characters only.
- Do not use an object name that already exists in the protected object space.
- Before deleting an object in the
dynurl.conffile, remove any ACLs attached to the object. - If Reverse Proxy receives a POST body that contains characters that are not UTF-8 or not from the character set (code page) used by Reverse Proxy, Reverse Proxy will reject the request.
- Because dynamic URL evaluation operates on all requests and uses character pattern matching, any requests containing binary data in the query string (GET) or request body (POST) is rejected with a 500 Server Error.