Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

content is not correct encode #86

Closed
siqiniao opened this issue Sep 3, 2019 · 1 comment
Closed

content is not correct encode #86

siqiniao opened this issue Sep 3, 2019 · 1 comment

Comments

@siqiniao
Copy link

siqiniao commented Sep 3, 2019

image
image

content should be urlencoded,but now is %uxxx, so my api get request params is like
{"content":"%u4E2D%u56FD"}

not the original string

@abhijitkane
Copy link
Member

@siqiniao Starting Postman 7.7.2, we've introduced bug-fixes, support for two new languages (JS-Fetch and Powershell), and the ability to configure certain aspects of the generated snippet with the 'New Code Generation Mode' flag enabled in Postman's global settings.

This particular problem has been solved as well.

Hope this addresses your concerns.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants