I have installed Katalon 5.5 in my machine. I tried to hit api which contains umlaut characters (German language) has one of the parameter and it is throwing 400 bad request error. But the same api is working fine in Soapui version 5.4.0 [image] [image]

Please send us your request file (.rs file). Regards

I am experiencing something similar here: When sending a request which contains an umlaut in the search string (“zür”) from the object repository I am getting a response with the content I am expecting (I don’t mind the garbled display in the reponse field): [image] When I send the same request w…

Hi @marcel.a , Please send us the HAR file logged in the console view

[image] marcel.a: I don’t mind the garbled display in the reponse field If you mind the garbled characters, there is a fix for it. See [image] Katalon.ini should speciify -Dfile.encoding=utf-8 Feature Request My experiment I use Katalon Studio v6.1.…

Hi @huynguyen Please find attached the two HAR files. The one for the request from object repositry which delivers a good response, and also the one from the testcase which delivers a “faulty” response… Thanks, Marcel ReqTestcase.har (3.6 KB) ReqObjRep.har (35.9 KB)

Hi @kazurayam Thanks for your response, I’ll try that after my initial problem is solved. Cheers, Marcel

[image] marcel.a: a request which contains an umlaut in the search string (“zür”) f The umlaut may be garbled in the request. It may cause 400 Bard Request error. So I would suggest to you to fix encoding problem first.

Hi @marcel.a , I can see from the har file that your requests sent from your test case script and from the Object Repository differs in Authorization header value. Can it be the reason why the responses are different for the two requests? Regards.

Hi @huynguyen Thanks for getting back to that topic. No, I don’t think the authorization header makes the difference. In the meantime I managed to get the test cases working. When encoding the Umlaute with percent-encoding aka URL-encoding ( https://en.wikipedia.org/wiki/Percent-encoding ) it works…

[image] marcel.a: I am experiencing something similar here: When sending a request which contains an umlaut in the search string (“zür”) from the object repository I am getting a response with the content I am expecting (I don’t mind the garbled display in the reponse field): [4a423d778533dc…

Getting 400 error (Bad Request) when hitting api response contains umlaut (german language) as one of the parameter

Bug Report

kazurayam September 7, 2019, 9:32pm 5

If you mind the garbled characters, there is a fix for it. See