You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Yes, because your browser doesn't send the X-Parse-Application-Id header which is required to authenticate. And 403 means that the app id that was sent (none) is unauthorized (forbidden).
Hi~
I followed a Parse-Server, and completed.
And I tested that it passed a data by POST, GET.
This far no problems.
So, http://localhost:1337/parse URI responsed a 403 error in browser.
Is this expected?
Thanks for your attention.
The text was updated successfully, but these errors were encountered: