-
Notifications
You must be signed in to change notification settings - Fork 855
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
Wrong curl import #7390
Comments
Thanks @m3dbedb - we'll aim to get a fix out soon. |
the issue in present in postman 7.11 |
In postman 7.18.1 for windows 7 32 bit curl body imports to x-www-form-urlencoded key, and recipient does not understand it
result
I suppose curl body should be imported as raw text:
|
@m3dbedb The default interpretation of
through the command line will send the JSON as the urlencoded key. As you suggested, specifying --data-raw and the json content type works:
Closing this issue - Postman's behavior is at par with the curl CLI. |
Describe the bug
Postman parses culr body imported as raw text to URL
To Reproduce
Steps to reproduce the behavior:
curl -i http://192.168.0.1:8084/api/v1/crontab -d '{
"name": "test10",
"description": "тестовое расписание",
"start": "2 * * * *",
"enable": true,
"command":"startTariff",
"param":"[123]"
}'
Expected behavior
In previous version 7.x.x Postman imported curl commands correctly, URL
-i http://192.168.0.1:8084/api/v1/crontab
appears in Request URL,-d '{ "name": "test10", "description": "тестовое расписание", "start": "2 * * * *", "enable": true, "command":"startTariff", "param":"[123]" }'
was moved to Request body.Screenshots
![curl](https://user-images.githubusercontent.com/25632818/65682088-e8e13180-e062-11e9-88f2-ddd72227e647.jpg)
applied
App information
The text was updated successfully, but these errors were encountered: