Symptoms

If any query parameters were added into request URL after being processed with F5 rewriting code, backend application could receive URL with wrong query separator (';').

Impact

Applications expecting '&' as a query separator won't be able to parse query part of URL correctly and may return an error.

Conditions

This occurs on Access Portal, some POST request parameters may have a semicolon as a query separator and not get rewritten.

Workaround

when REWRITE_REQUEST_DONE { # Replace parameter_name with actual name of parameter which is added after F5CH. if { [HTTP::query] contains {;parameter_name=} } { HTTP::query [string map {;parameter_name= &parameter_name=} [HTTP::query]] } }

Fix Information

Now requests to back-end server with query parameters contain parameter delimiters from original web application request.

Behavior Change