passing serverURL argument to ParseServer #66
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
I'm finding that if I don't pass the serverURL argument into the newly created ParseServer, any queries that I run in cloud code fail with 401-unauthorized. I tracked this down to be because it was sending the query requests to api.parse.com.
|
Yes it should be. It likely will be in the next version, we are discussing the details in parse-community/parse-server#464 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I'm finding that if I don't pass the serverURL argument into the newly created ParseServer, any queries that I run in cloud code fail with 401-unauthorized. I tracked this down to be because it was sending the query requests to api.parse.com.
Does this imply that the serverURL argument should be mandatory?