Surely it’s the “=” within the query predicate that should be escaped, not the one immediately after _xql?
The rules for URLs suggest that any “=” sign within a query parameter should be escaped as %3D. However, some products seem to be more tolerant than others, some will happily accept a URL query parameter of the form a=b=c as meaning that parameter “a” has the value “b=c”, but others throw it out or process it incorrectly. I haven’t got to the bottom of this, but it is clear that officially (according to RFC2396) special characters such as “=” (and “[” and “]”, for that matter) should be escaped, and if you get away without escaping it, then the web server is just being kind to you.
Michael Kay
#webMethods#API-Management#Tamino