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

blaze server fall into inconsistency when handling adding some invalid file resource #1498

ywang007 opened this issue May 4, 2016 · 0 comments


Copy link

commented May 4, 2016

When trying to add dataset to blaze server (via /add route), if the underlying file resource is given incorrectly, in some cases, the blaze server will return 422 error, but from now on fall into bad internal state (subsequent /datashape call returns 500 error).

Those cases are:

  1. invalid relative path, such as ./badfile; ../badfile;
  2. invalid absolute path that ends with valid file ext, such as:

However, an when the invalid absolute path does not end with a valid file ext, such as:

Then the blaze server will simply return 422 error, and still in working state.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
2 participants
You can’t perform that action at this time.