Skip to content

Cache idempotent requests responses #9294

Open
@abubkr-hago

Description

@abubkr-hago

New Feature / Enhancement Checklist

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    type:featureNew feature or improvement of existing feature

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions