fix: align PaymentBodyLayer retry and cache semantics - #313
Open
vikions wants to merge 1 commit into
Open
Conversation
This file contains hidden or 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
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.
Summary
WWW-Authenticatechallenge withCache-Control: no-storeafter failed payment verificationprivatewhile preserving existing cache directivesMotivation
PaymentBodyServicediverged from the standardPaymentServicebehavior in two protocol-relevant paths:Payment-Receiptdid not receive private cache semanticsBody-digest binding should not change the retry lifecycle or receipt caching behavior of the Tower payment middleware.
Testing
cargo test --lib body_service --no-default-features --features towercargo fmt --checkcargo clippy --lib --no-default-features --features towergit diff --checkAll focused tests pass. Clippy reports only pre-existing cfg-dependent warnings unrelated to this change.