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

Run Collection - returns server error 500 #5615

Closed
GitHubHelps opened this issue Dec 6, 2018 · 1 comment
Closed

Run Collection - returns server error 500 #5615

GitHubHelps opened this issue Dec 6, 2018 · 1 comment

Comments

@GitHubHelps
Copy link

Describe the bug
I have create POST method to upload file/image through Body - form-data - file. If i run the request like a singe request is totally OK, because we DON'T put image/file (see picture 2), but if I run the same request through collection runner I got server error 500 and all other test are terminated! (see picture 1)

To Reproduce
Steps to reproduce the behavior:

  1. Go to postman and run POST method with Body - form-data - file.
  2. Don't load file/image
  3. Run the request
  4. We got "400 Bad Request" (this is correct!)
  5. Run the same request through Collection runner
  6. The error now is "500 server error" and all other test are terminated!

Expected behavior
The error is "400 Bad Request" just like we push single request (picture 2)

Screenshots
image
image

App information (please complete the following information):

  • Postman app
  • Postman Version 6.5.3
  • OS: Windows 10 Enterprise
@sivcan
Copy link
Member

sivcan commented Dec 6, 2018

Hi @GitHubHelps, the issue is that we do not store file path's in the app due to security reasons.
So, in the runner the file paths don't work for now.
But we'll be building upon a better way to solve this problem.

Here's more info explaining the issue of storing file paths in the app: #4824 (comment)

You can follow the thread above and it refers #4320 ticket, which aims to solve the problems of file path storage in the app.

I regret the inconvenience caused.
I'll be closing this issue since we're tracking the file path issue already.
Kindly follow the above mentioned thread for updates.

Thank you!

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