parse-community / parse-community/parse-server
Cache idempotent requests responses
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 21.4k
- Forks
- 4.8k
- Avg merge
- 7h 45m
- Merged PRs (30d)
- 11
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
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how Parse Server handles repeated requests with the X-Parse-Request-Id header and where the 159 error is produced. Define the response data that would need to be retained and replayed, then verify that a repeated object-creation request returns the original response without creating a duplicate.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100