I am writing to report an issue I encountered while developing my application using the Parse SDK. Specifically, I am experiencing a problem related to URL escaping, particularly when using the whereRelatedTo method.
Context:
I have integrated the Parse SDK into my application to interact with a Parse server via its REST HTTP API. However, I have discovered that when using the whereRelatedTo method from the Parse SDK, an error occurs due to incorrect URL escaping.
Issue Description:
Upon making requests using the Parse SDK's whereRelatedTo method, the server consistently responds with an internal server error. After further investigation, I found that the error is related to URL escaping. I have observed that when manually constructing and sending the request using CURL, following the API documentation guidelines and proper URL encoding, the error does not occur.
Example:
Computed URL with incorrect escaping using Parse SDK:
🚀 You can help us to fix this issue faster by opening a pull request with a failing test. See our Contribution Guide for how to make a pull request, or read our New Contributor's Guide if this is your first time contributing.
New Issue Checklist
Issue Description
I am writing to report an issue I encountered while developing my application using the Parse SDK. Specifically, I am experiencing a problem related to URL escaping, particularly when using the whereRelatedTo method.
Context:
I have integrated the Parse SDK into my application to interact with a Parse server via its REST HTTP API. However, I have discovered that when using the whereRelatedTo method from the Parse SDK, an error occurs due to incorrect URL escaping.
Issue Description:
Upon making requests using the Parse SDK's
whereRelatedTo
method, the server consistently responds with an internal server error. After further investigation, I found that the error is related to URL escaping. I have observed that when manually constructing and sending the request using CURL, following the API documentation guidelines and proper URL encoding, the error does not occur.Example:
Computed URL with incorrect escaping using Parse SDK:
Server response
Working CURL command with proper URL encoding:
Url escaped using curl and saved using curl option
--trace-ascii
Parse Flutter SDK
5.1.2
3.10.5
3.0.1
Arch Linux, Linux 6.3.8-zen1-1-zen x86_64
Server
4.5.0
(hosted by back4app)