-
Notifications
You must be signed in to change notification settings - Fork 846
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
Unify line endings in Request Body #4179
Comments
Hi @Geolim4, this looks super weird. Can you open up the Postman Console (Ctrl+Alt+C), and resend your request? You should see the request in the Console. Can you check if the request body is in here? |
Okay, after looking the console I found out the issue. Postman send Windows line ending (\r\n) instead of Unix line ending (\n), therefore the web server is unable to natively parse correctly the body content :( When I manipulated k/v in bulk edit mode Postman reformatted the line ending to Unix one... In the end, i'm not sure if this bug is really Postman-related or php7-related... |
@madebysid What's are your thoughts about this ? |
I think I'm having the same problem. Calling the endpoint via Paw works fine, but not with Postman. |
@aroblu94 Yes by forcing line-ending on the server side :) |
@Geolim4 We're glad that you could make it work. Howerver, Postman as a client should be handling this type of requests. I'm reopening this to track a fix for this in Postman. |
App Details:
Issue Report:
When sending a request postman is sometimes failing to sent the data.
I send the data as a x-www-form-encoded with key/value and to get it working I had to switch from bulk edit to kv edit multiple times before I can receive the data on the webserver side.
I noticed this issue since I migrated to Postman for Windows, I did not have this issue with Chrome app tho.
This issue is getting very annoying :(
The text was updated successfully, but these errors were encountered: