Solved: New Proxy Editor (15.07) will not allow XML encodi... - Page 2

Report Inappropriate Content · 11-10-2015 08:32 AM

When I am trying to define some RegEx expressions in the RegularExpressionProtection policy (my SQL Injection protection) using Apigee Edge 15.07, I need to include "<" and ">" in the expression. Since I am defining it inside XML, I can't use the symbols as-is, and am trying to use "<" and ">" instead. HOWEVER, apigee keeps converting them back to "<>", and then will not let me save the policy as the symbols are invalid for XML.

If I switch to the old version of the editor (15.04), I can save just fine, but the new version (15.07) seems to be running a script (I am using Chrome) to try to convert my XML encoding back, and when it does, it complains about lack of encoding. Is there a bug in 15.07 dealing with XML characters in XML Policy editor???

Report Inappropriate Content

So I know I'm late to this, but one workaround (not ideal) is to double up your xml-encoding.

So to take from the server-side include Reg Ex protection policy pattern:

<!--\s*<!--(include|exec|echo|config|printenv)\s+.*

Would need to be put into the editor as:

&lt;!--\s*&lt;!--(include|exec|echo|config|printenv)\s+.*

And then it will save as your intended encoding (the first one).

Like I said, it's not ideal, but if you have to work with the UI editor then it is a workaround to inform your proxy developers about.

-----------

A coworker pointed out that another option is to use the old editor briefly to add the xml-encoded text, save, then return to the new editor.

View solution in original post

New Proxy Editor (15.07) will not allow XML encoding - keeps converting back to characters not allowed