We observed below in one of the case where the URL Query Parameter has a "#" in it. Gateway is trimming the data after the "#" while receiving as shown in below example.
https://email@example.com&include=alldata Received URL in Gateway :
How this can be avoided? One option is to encode the url while invoking. But is there any other option as the consuming application does not want to encode the data.
The hash fragment of the URL is not supposed to be sent to the server (ie: the Gateway). It is to be sent to and processed by the browser.
Mohindra.Singh actually posted a sample policy below allowing you to retrieve and convert this to a query parameter that can be used by the Gateway:
Sample Policy for converting a URL hash fragment into a query parameter