Ask a Question

=,& characters are replacing with special Character

SOLVED
mrarkapravo
Contributor

=,& characters are replacing with special Character

Request type -GET

While reading & and = from excel and passing it as query parameter in SOAP UI for then value "&" ,"=" are replacing with %3D and %26 character and due to that i am not geting correct response ,So could anyone help  me out over here to resolve this issue ?

6 REPLIES 6
TwoFang
Contributor

It could be that all you have to do is change the Encoding to UTF-8 under the REST Request Properties tab to get it to work

Regards
/N

richie
Community Hero

Hi @mrarkapravo,

The behaviour (replacing special chars with percent encoding) is standard HTTP behaviour. This is because the :, =, /, & and a couple of others are reserved and have special meaning in HTTP requests.

You can disable the percent encoding but its inadvisable to do unless you have a good reason. On top of that i'm 100% that the issue youre having is not related to your characters being percent encoded....its caused by something else.

Double check and you'll see.

Suggest googling "percent encoding" or "html encoding" and this will explain things much better than i have!

Cheers,

Rich
if this helped answer the post, could you please mark it as 'solved'? Also if you consider whether the title of your post is relevant? Perhaps if the post is solved, it might make sense to update the Subject header field of the post to something more descriptive? This will help people when searching for problems. Ta

Thank you for your response ,i checked from my end as per your answer but unable to resolve .

Thank you for your reply ,I could not able to looked into the solution you had provided but the below helped me .
https://community.smartbear.com/t5/SoapUI-Pro/The-quot-Disables-URL-Encoding-of-the-parameter-value-...

Reagrds !!

Arka

Hi @mrarkapravo

I understand youve found a workaround to get you going again, but the fact that your listening webservice isn't accepting percent encoding (which is standard for HTTP traffic) indicates there is likely an issue somewhere that needs fixing.
I'd mention this to a lead developer or software architect, cos they'll want to identify why your endpoint isn't accepting an web/HTTP standard.

Cheers!

Rich
if this helped answer the post, could you please mark it as 'solved'? Also if you consider whether the title of your post is relevant? Perhaps if the post is solved, it might make sense to update the Subject header field of the post to something more descriptive? This will help people when searching for problems. Ta

I agree and that's right ,thanks again for your prompt attention.

Kind regards -
Arka
cancel
Showing results for 
Search instead for 
Did you mean: