Encoding of URL paths is incorrect

[armpogart]

App Details:

Postman for Windows
Version 5.3.2
win32 10.0.16299 / x64

Issue Report:

1. I use the request that is working in chrome app, but in native app I get incorrect symbols in header response from the API server, it's something with request encoding, I have russian characters in request endpoint name and it is working ok in chrome app. Request is something like http://endpoint:port/odata/standard.odata/Catalog_Пользователи?$format=json
2. Expected behaviour: correct response
3. In Dev Tools console I see one error - Failed to load resource: net::ERR_FILE_NOT_FOUND - mode-auto.js

[armpogart]

Maybe something related to #2263

[armpogart]

Also if I encode url manually and use the encoded string there - everything is working.

[sdnts]

@armpogart Thanks for reporting this, we will investigate this. @kamalaknn This looks related to runtime. Related: #3734, #3765

[armpogart]

Any progress on this one?

[shamasis]

Note: We need more details, perhaps a scaled down collection and/or endpoint to reproduce this.

[armpogart]

@shamasis I guess any endpoint with Cyrillic letters in url. In my case it was 1C platform with it's odata endpoints. Unfortunately the endpoint I was working with is private and I don't have any public one at this moment.

[gdomo]

Postman 6.4.4
Ubuntu 18.04.1 LTS

абвгдеёжзийклмнопрстуфхцчшщьыъэюяАБВГДЕЁЖЗИЙКЛМНОПРСТУФХЦЧШЩЬЫЪЭЮЯ

turns in
012345Q6789:;<=>?@ABCDEFGHILKJMNO����������������� !"#$%&'(),+*-./

Example:

[shamasis]

Closing it as a duplicate in master issue: #4555

[codenirvana]

This is fixed in the latest version of the Postman app (v7.20.0) by enabling the "Use next generation URL processing" setting as mentioned in #8154.