Skip to content

fix: proxy must not ACK 2xx final responses - #146

Open
nbasil wants to merge 1 commit into
restsend:mainfrom
nbasil:fix/proxy-no-ack-2xx
Open

nbasil wants to merge 1 commit into
restsend:mainfrom
nbasil:fix/proxy-no-ack-2xx

Conversation

@nbasil

@nbasil nbasil commented Sep 24, 2026

Copy link
Copy Markdown

Fixes #145

Per RFC 3261 (§16.7, §17.1.1.3), the ACK for a 2xx final response is
end-to-end and generated by the UAC, so a proxy must not send one
itself. This change stops the proxy from ACKing 2xx responses; ACKs for
non-2xx final responses are unchanged.

Verified with cargo fmt, cargo build, cargo test (all passing), and
cargo clippy --lib (no new warnings).

Note: cargo clippy --lib reports one pre-existing warning (drop_non_drop,
src/dialog/invitation.rs), also present on v0.6.6; unrelated and left untouched.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Client INVITE transaction auto-ACKs 2xx final responses — incorrect for proxy use (RFC 3261 section 17.1.1.2), and not suppressable from outside

1 participant