Conversion of POST body dynamic data to query string format

When you map a URL regular expression to an object space entry, the query string format as produced from the GET request method must be used—regardless of the request method (POST or GET).

In a GET request, the dynamic data (operations, parameters, and values) provided to the Web application interface are located in the query string portion of the request URL.

In a POST request, the dynamic data (operations, parameters, and values) provided to the Web application interface are located in the request body.

To maintain the required query string structure required for access control evaluation, the POST request body should be in the query string format, as is done with the default POST media type of application/x-www-form-urlencoded. For example, a POST request has the following request URL:

http://server/login.form

Dynamic data (login information provided by the user) is located in the body of this POST request:

name=ibm&password=secure

To achieve the query string structure required for dynamic URL evaluation, WebSEAL appends the POST body information to the request URL:

http://server/login.form?name=ibm&password=secure

If the request body uses a different media type, such as multipart/form-data, and might include unencoded binary or reserved URL characters, the [server] suppress-dynurl-parsing-of-posts parameter should be set to 'yes'.

Parent topic: Access control for dynamic URLs