-
Notifications
You must be signed in to change notification settings - Fork 837
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
Could not get any response cause - Error: Parse Error #5704
Comments
@testica Is there a publicly accessible endpoint we could use to replicate this? |
@numaanashraf no, sorry. It's a private local service. |
@testica Thanks. Could you share the request and response headers from curl or postman chrome extension? |
@numaanashraf For response headers:
|
I know that my error is not exactly the same, but only for information usually its a webserver or app response headers problem. For example, I configure my webserver to accept CORS according to enable-cors.org, everything is working fine through curl and browser but not in postman. So I decided to check response header Basically I changed the webserver configuration and now Postman is able to parse my application response headers, the bug is in parse response. This is my context: Like I said, its just to show from us(customer users) that usually is our side issue (webserver response), but would be great if the postman console error shows more information. |
I had misconfigured strict transport HTTP headers in my response which caused the "Error: Parse Error" in Postman. I had to use third party tools to debug this though, I sure would love plaintext request/response output with this error in the console to help me. Additionally the user friendly message says "There was an error connecting to..." which suggested to me a network or DNS problem at first. Perhaps this could be more generic. |
Having this same problem with a custom C++ server. std::string output = oss.str(); Firefox receives this just fine, but Postman give me the same parse error mentioned here. |
Hi everyone. Apologies for jumping in late. Parse Error can be reached due to a failure from multiple flows. We are tracking some edge cases where we get parse error, but not sure if the ones mentioned here map on to those. "Works in browser X" is not helping us isolate what exactly the issue is. I would love to have this tested via getting access to a shareable collection and either a publicly available server or a simple node/python code snippet that emulates this locally. |
Hi all, especially @testica @ghostravenstorm @pvgomes, I am closing this issue for now. Two reasons:
My hunch is that @testica, the server that is returning response is a device that is behaving slightly non-compatible with general HTTP cases handled by Postman. I will be happy to get into more detailed discussions to debug this. In case you have things that you cannot post publicly, please reach out to help@getpostman.com @pvgomes ... your case, like you mentioned, is strange and interesting. Can you file a separate issue with the strange headers in question. An easy way for you to help us make it reproducible is make the request and then replace the URL with applicable https://postman-echo.com/ url and see if it is still reproducible. If yes, then simply share the collection with us. We will definitely get it sorted. |
I am fetching a JSON, but postman show me the message "Could not get any response" and postman console show:
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Json response:
App information:
Additional Information:
I make the same request from curl and postman chrome extension and it works. The issue happens in the native app.
The text was updated successfully, but these errors were encountered: