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
I have an existing Parse database with various types of information in it. I am able to get objects and use the basic functions. When I try to find an object by matching a regex expression (e.g. label_regex='$1234' on a String type in Parse, the operation fails. I am able to do this operation using the Parse Server API console.
The issue appears to be that the query manager is attempting to URL encode the escape characters and it should not be doing that. I have C++ code that performs various tasks with the Parse API and it rejects requests which include escape sequences.
The text was updated successfully, but these errors were encountered:
I have an existing Parse database with various types of information in it. I am able to get objects and use the basic functions. When I try to find an object by matching a regex expression (e.g. label_regex='$1234' on a String type in Parse, the operation fails. I am able to do this operation using the Parse Server API console.
The issue appears to be that the query manager is attempting to URL encode the escape characters and it should not be doing that. I have C++ code that performs various tasks with the Parse API and it rejects requests which include escape sequences.
I have an existing Parse database with various types of information in it. I am able to get objects and use the basic functions. When I try to find an object by matching a regex expression (e.g. label_regex='$1234' on a String type in Parse, the operation fails. I am able to do this operation using the Parse Server API console.
The issue appears to be that the query manager is attempting to URL encode the escape characters and it should not be doing that. I have C++ code that performs various tasks with the Parse API and it rejects requests which include escape sequences.
The text was updated successfully, but these errors were encountered: