Hi,
the ACE is not changing the behaviour, it's the client's browser. It does appear that the ACE is changing the POST to a GET but isn't.
As an example, a client browser sends a POST and the ACE receives the POST. For a redirect, the ACE responds back to the client with either a 301 or 302 code.
Here's where everything goes sideways ....
The client browser receives the redirect code, but this isn't what it is expecting to receive from a POST. In turn, the client browser now sends a GET back to the ACE. The ACE receives the GET and forwards onto the load balanced servers that, in turn, aren't expecting this. Application fails because of this.
Regards,
Steve