Skip to content

backport 1.17: wasm: fix getHeaderMapValue() in case of early client disconnect. (#1…#15395

Merged
Shikugawa merged 2 commits intoenvoyproxy:release/v1.17from
Shikugawa:backport-1.17/15224
Mar 15, 2021
Merged

backport 1.17: wasm: fix getHeaderMapValue() in case of early client disconnect. (#1…#15395
Shikugawa merged 2 commits intoenvoyproxy:release/v1.17from
Shikugawa:backport-1.17/15224

Conversation

@Shikugawa
Copy link
Member

…5224)

Previously, getHeaderMapValuei() would incorrectly return BadArgument
when called in the access log phase after an early client disconnect,
because the code assumed that a HeaderMap can point to a nullptr only
when called from a callback in which given map is not available.

Fixes proxy-wasm/proxy-wasm-rust-sdk#82.

Signed-off-by: Piotr Sikora piotrsikora@google.com
Signed-off-by: Shikugawa rei@tetrate.io

For an explanation of how to fill out the fields, please see the relevant section
in PULL_REQUESTS.md

Commit Message:
Additional Description:
Risk Level:
Testing:
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Deprecated:]
[Optional API Considerations:]

…voyproxy#15224)

Previously, getHeaderMapValuei() would incorrectly return BadArgument
when called in the access log phase after an early client disconnect,
because the code assumed that a HeaderMap can point to a nullptr only
when called from a callback in which given map is not available.

Fixes proxy-wasm/proxy-wasm-rust-sdk#82.

Signed-off-by: Piotr Sikora <piotrsikora@google.com>
Signed-off-by: Shikugawa <rei@tetrate.io>
@Shikugawa Shikugawa changed the title wasm: fix getHeaderMapValue() in case of early client disconnect. (#1… backport 1.17: wasm: fix getHeaderMapValue() in case of early client disconnect. (#1… Mar 10, 2021
Copy link
Contributor

@PiotrSikora PiotrSikora left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

…nto backport-1.17/15224

Signed-off-by: Shikugawa <rei@tetrate.io>
@Shikugawa Shikugawa merged commit c1eeffe into envoyproxy:release/v1.17 Mar 15, 2021
@Shikugawa Shikugawa deleted the backport-1.17/15224 branch March 15, 2021 13:52
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.

2 participants