Is Encode / Decode Data Assertion compliant with RFC3986?
Decode Data Assertion URL encoding does not encode "*" (asterisk).
This is an RFC3986 reserved character.
Also, "~" (tilde) is encoded.
This is an RFC3986 unreserved character.
In the above result, the characters to be encoded are different from the rules of RFC3986.
Release : 10.0
Component : API GATEWAY
We strive to be RFC complaint but may not always be able to do so.
If the current results are inconvenient for your operation, please contact Brodcom Support.