Forum Discussion
hooleylist
May 24, 2010Cirrostratus
So it looks like the member selection is succeeding in that the .65:80 member is selected for both requests. Is that what you're seeing?
Is it possible that the application isn't handling the manually inserted parameter name/value? You could test this by removing it from the URI in HTTP_REQUEST before the request is sent to the pool member:
Use a workaround to parse the parameter value from the query string
described on http:// devcentral.f5.com/wiki/default.aspx/iRules/uri__query
set param_value [URI::query "?&[HTTP::query] "&$member_param"]
Save a copy of the URI with the param and value removed
set uri [string map [list "$member_param=$param_value" ""] [HTTP::uri]]
Replace && with & in the updated query string if && is present and set the URI to this
HTTP::uri [string map "&& &" $uri]
Aaron