302 Redirect Location Header Rewrite not working with code upgrade

Question

Hi,
Description:
We have a portal webservice hosted by an ACE4710. It has two services (www/https) on the same IP 10.1.1.1.
One is a redirect service that redirects all requests to tcp/80 on this ip to the other which is a 'standard' https proxy service.
The backend servers are http only. Externally everything needs to be https.
So we have an ssl proxy and Location header http to https rewrite on the https service.
The configuration below operates correctly on v5_1_2.
But with a code upgrade to 5_3_1b, the Location header rewrite does not work.
We've tried several different configurations and even 'ssl url location rewrite ".*". It just looks like the ACE is completely ignoring the configuration to rewrite the Location field.
Reverting to the older code fixes the problem.
Problem seen:
Here is the problem as seen on the *client*. The 302 redirect Location header is NOT rewritten:
Response headers:
HTTP/1.1 302 FOUND
Server: nginx
Date: Fri, 20 Mar 2015 10:59:43 GMT
Content-Type: text/html; charset=utf-8
Content-Length: 295
Connection: keep-alive
Location: http://website.liveportal.nhs.uk/homepage/information
Cache-Control: no-cache, no-store
Set-Cookie: information=35a7831d-928d-4122-aef3-39ef48ac4440; Path=/; secure; HttpOnly
X-Frame-Options: DENY
HTTPSampleResult fields:
ContentType: text/html; charset=utf-8
DataEncoding: utf-8
Config extract:
1) Set up the servers (4 normal on tcp/80 and one for a redirect)
rserver host WEBSERVICE-1
  ip address 192.168.1.1
  conn-limit max 200000 min 160000
  inservice
...and the same for the other three
rserver redirect PORTAL_REDIRECT
  webhost-redirection https://%h/%p 302
  inservice
2) Set up the server farms
serverfarm host PORTAL_LIVE
  probe webping
  rserver WEBSERVICE-1 80
    inservice
  rserver WEBSERVICE-2 80
    inservice
  rserver WEBSERVICE-3 80
    inservice
  rserver WEBSERVICE-4 80
    inservice
serverfarm redirect PORTAL_HTTP_REDIRECT
  rserver PORTAL_REDIRECT
    inservice
3) Setup the ssl proxy and a location rewrite to https for responses from the servers
action-list type modify http HTTPS_LOCATION
  header rewrite response Location header-value "http://(.*)" replace "https://%1"
ssl-proxy service WEB_SSL_PROXY
  key webportal.key
  cert webportal.crt
  chaingroup root-chain
  ssl advanced-options SSL-SECURE-STRONG-WEB
4) Set up the L4 services
class-map match-all PORTAL_HTTP
  2 match virtual-address 10.1.1.1 tcp eq www
class-map match-all PORTAL_SSL
  2 match virtual-address 10.1.1.1 tcp eq https
5) Setup the policy maps - one for the reals servers with header rewrite for redirects
policy-map type loadbalance http first-match PORTAL_HTTP
  class class-default
    serverfarm PORTAL_HTTP_REDIRECT
policy-map type loadbalance http first-match PORTAL_SSL
  class class-default
    serverfarm PORTAL_LIVE
    action HTTPS_LOCATION
6) Create the service policy
policy-map multi-match EXTERNAL-SERVICES
  class PORTAL_SSL
    loadbalance vip inservice
    loadbalance policy PORTAL_SSL
    loadbalance vip icmp-reply
    appl-parameter http advanced-options PARAM-HTTP
    ssl-proxy server WEB_SSL_PROXY
  class PORTAL_HTTP
    loadbalance vip inservice
    loadbalance policy PORTAL_HTTP
    loadbalance vip icmp-reply
7) Apply to the interface
interface vlan 211
  description External Access
  ip address x.x.x.x 255.255.255.0
  alias x.x.x.x 255.255.255.0
  peer ip address x.x.x.x 255.255.255.0
  access-group input PERMIT-ALL
  service-policy input EXTERNAL-SERVICES
  no shutdown

Answer 1

I found that the v5_3_1b code seems to need a bit of extra configuration and it now works ok.
parameter-map type http PARAM_HTTP
header modify per-request
no persistence-rebalance
case-insensitive