Open
Description
New Feature / Enhancement Checklist
- Report security issues confidentially.
- Any contribution is under this license.
- Before posting search existing issues.
Current Limitation
Idempotent requests are now rejected with a 159
code error,
Feature / Enhancement Description
Instead of rejecting with an error, maybe there is a way to cache the response and respond with it on the next request?.
Example Use Case
A client SDK creates a Test
ParseObject but doesn't recieve the response because of a network issue, the SDK tries to create the object again with the same X-Parse-Request-Id
header, the server replies with the same object creation response instead of creating a new one.
Alternatives / Workarounds
N/A
3rd Party References
N/A