Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(proxy-wasm) resume the filter chain on dispatch response #428

Closed
wants to merge 1 commit into from

Conversation

thibaultcha
Copy link
Member

The dispatch could be during on_request_body, and when the response is received, subsequent filters' on_request_body steps should also be invoked.

This is a rudimentary fix for the time being, but now that the proxy-wasm runloop is fully re-entrant, the resume model could also be refactored into something cleaner and reusable for other C resume handlers.

The dispatch could be during `on_request_body`, and when the response is
received, subsequent filters' `on_request_body` steps should also be
invoked.

This is a rudimentary fix for the time being, but now that the
proxy-wasm runloop is fully re-entrant, the resume model could also be
refactored into something cleaner and reusable for other C resume
handlers.

Co-Authored-By: Caio Ramos Casimiro <[email protected]>
@codecov
Copy link

codecov bot commented Oct 6, 2023

Codecov Report

Merging #428 (583cb4c) into main (1db400a) will decrease coverage by 0.02263%.
The diff coverage is 100.00000%.

Additional details and impacted files

Impacted file tree graph

@@                 Coverage Diff                 @@
##                main        #428         +/-   ##
===================================================
- Coverage   90.14168%   90.11905%   -0.02263%     
===================================================
  Files             46          46                 
  Lines           8399        8400          +1     
===================================================
- Hits            7571        7570          -1     
- Misses           828         830          +2     
Files Coverage Δ
src/http/ngx_http_wasm_module.c 96.38889% <ø> (-0.55555%) ⬇️
src/http/proxy_wasm/ngx_http_proxy_wasm_dispatch.c 91.76136% <100.00000%> (+0.02347%) ⬆️
src/wasm/ngx_wasm_ops.c 90.95745% <ø> (ø)

@thibaultcha thibaultcha closed this Oct 6, 2023
@thibaultcha thibaultcha deleted the fix/proxy-wasm-chain-on-dispatch-response branch October 6, 2023 15:19
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.

1 participant