PPM 9.22.0003 + Firefox 33 = broken Request Rules.
Like Chrome, Firefox 33 brokes totally PPM's Request Rules.
For example if you have a request on load rule, and uses [REQ.REQUEST_ID] token, the Rule is not properly fired.
So, actually PPM 9.22.0003 is unusable for our organization.
Is there any quick and dirty workaround for this ?
Indeed, I've created a case support and provided a deep "How to reproduce" this issue.
Today we have discovered some bad side effects : any Request Rule who use [REQ.REQUEST_ID] is broken.
The only workaround is : ban Chrome and Firefox with our front-end Apache Web Server, and put a message to invite users to user Internet Explorer.
Since Mozilla Firefox is our corporate browser, this solution put our team in a very delicate situation.
Did HP told you anything about this happening because of the patch 0003 or is just a firefox thing? If any of both are they going to patch it?
This issue comes from Firefox 33.
HP has created a known issue document for this case :
I don't have any other information about this issue. We are waiting for R&D answser.
PPM 9.30 documentation has been updated today.
Apparently only Firefox ESR 24 is actually supported.
Source : PPM 9.30 What's new (3rd edition).
we faced the same issue and it disappeared with HP PPM 9.31 using the following browser versions:
Mozilla Firefox 31 ESR (with 38 ESR the issue is still present - but this version is not officially supported)
Google Chrome 42