Are you running Actions URI 1.7.2 yet? Because it (supposedly) contained a fix/workaround for exactly that issue: Release: Actions URI 1.7.2
Are you running Actions URI 1.7.2 yet? Because it (supposedly) contained a fix/workaround for exactly that issue: Release: Actions URI 1.7.2