Update draft-ietf-httpapi-idempotency-key-header.md #24
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@sdatspun2 @dret Can you help with the merging? |
|
@vikiuvb is there any plan to use the proposed Idempotency-Key header and deprecate Chargebee's customer http header? FYI, this section will be removed in future. Till then, we would love to add more implementers rather than those implementing concept. |
|
@sdatspun2 Thanks for your response. We are using custom headers currently for some internal reasons. However, we will soon deprecate this header and use the "Idempotency-Key" header. Except for the header part, our implementation adheres to the specification. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Included Chargebee in the implementations