Query parameter values starting with # is not getting considered in Postman

Question

I developed one application in Mulesoft for calling a SOAP webservice. While making GET call to a SOAP web service from Postman, query parameter value starting with # is not getting considered by my Mulesoft mapping.

e.g: http://localhost:8080/appName?queryParam1=#abc

In my mule application, the value for queryParam1 is coming as empty value. Could some one explain the technical reason for this. Is # is considered as escape character from Postman or Mulesoft Transform Message activity? Thanks in advance

Please see the answer here: https://stackoverflow.com/questions/29841137/what-is-the-behavior-of-hash-in-query-string — Brad Cooper, May 06 '18 at 22:26
A very good explanation around the technicality around using # is found in the link provided by by Brad Cooper. Thanks a lot, Brad. — ravindra babu, May 10 '18 at 16:44

score 0 · Answer 1 · answered May 07 '18 at 08:46

0

I also faced the same issue in my API, in URI anywhere in between comes the '#' character the rest of your URI will go blank and the 404 HTTP error will occur.

I suggest you to get the value in query parameter without # character and later in the API code or flow prefix it. This will work.

Hope this will resolve your problem.

answered May 07 '18 at 08:46

Kunal Gupta

46
4

Yes Kunal, you are correct. But we can encode the # with %23 as suggested by Sagar. Thanks for your response. – ravindra babu May 10 '18 at 16:25

score 0 · Answer 2 · answered May 07 '18 at 14:50

0

You will have to encode characters such as #. Refer this link for complete list of such characters. In your example:

Change: http://localhost:8080/appName?queryParam1=#abc

To: http://localhost:8080/appName?queryParam1=%23abc

answered May 07 '18 at 14:50

Sagar Chaudhari

155
5

Query parameter values starting with # is not getting considered in Postman

2 Answers2