Skip to content

Internal server error #101

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

Closed
doender opened this issue Jan 31, 2016 · 2 comments
Closed

Internal server error #101

doender opened this issue Jan 31, 2016 · 2 comments
Labels
type:bug Impaired feature or lacking behavior that is likely assumed

Comments

@doender
Copy link

doender commented Jan 31, 2016

I migrated my Parse data over to a local instance. Most queries seem to work, but this one does not:

curl 
-H "X-Parse-Application-Id: myAppId"   
-H "Content-Type: application/json"   
http://localhost:1337/parse/classes/Test 
--data-urlencode 'where={"name":{"$exists":true}}'

I get:

{"code":1,"message":"Internal server error."}

The server log shows:

Uncaught internal server error. { [Error: invalid json]
  body: 'where=%7B%22name%22%3A%7B%22%24exists%22%3Atrue%7D%7D',
  status: 400 } Error: invalid json
    at parse (/vagrant/parse-server-example/node_modules/body-parser/lib/types/json.js:79:15)
    at /vagrant/parse-server-example/node_modules/body-parser/lib/read.js:102:18
    at done (/vagrant/parse-server-example/node_modules/raw-body/index.js:248:14)
    at IncomingMessage.onEnd (/vagrant/parse-server-example/node_modules/raw-body/index.js:294:7)
    at IncomingMessage.g (events.js:273:16)
    at emitNone (events.js:80:13)
    at IncomingMessage.emit (events.js:179:7)
    at endReadableNT (_stream_readable.js:906:12)
    at nextTickCallbackWith2Args (node.js:474:9)
    at process._tickCallback (node.js:388:17)
@gfosco
Copy link
Contributor

gfosco commented Feb 1, 2016

Ok, looks like another bug related to query strings... Will look in to it.

@nlutsenko
Copy link
Contributor

Fixed with #543.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:bug Impaired feature or lacking behavior that is likely assumed
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants