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

WASM to read some value from body and update headers accordingly #37196

Closed
kushagar opened this issue Nov 18, 2024 · 4 comments
Closed

WASM to read some value from body and update headers accordingly #37196

kushagar opened this issue Nov 18, 2024 · 4 comments
Labels
area/wasm question Questions that are neither investigations, bugs, nor enhancements stale stalebot believes this issue/PR has not been touched recently

Comments

@kushagar
Copy link

So I have a use case where I want to read a request body , take out a key and use it's value to update the headers before sending request to the upstream.But problem with proxy wasm is once request is passed to on_http_request_body function, I cannot update headers. Can someone help me with how I can work around this( I don't want to use lua).

@kushagar kushagar added the triage Issue requires triage label Nov 18, 2024
@soulxu
Copy link
Member

soulxu commented Nov 19, 2024

cc @kyessenov

@soulxu soulxu added question Questions that are neither investigations, bugs, nor enhancements and removed triage Issue requires triage labels Nov 19, 2024
@kyessenov
Copy link
Contributor

Please follow this issue proxy-wasm/spec#63. It requires a bump in ABI version, but it's a priority to support this use case.

Copy link

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or "no stalebot" or other activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the stale stalebot believes this issue/PR has not been touched recently label Dec 19, 2024
Copy link

This issue has been automatically closed because it has not had activity in the last 37 days. If this issue is still valid, please ping a maintainer and ask them to label it as "help wanted" or "no stalebot". Thank you for your contributions.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Dec 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/wasm question Questions that are neither investigations, bugs, nor enhancements stale stalebot believes this issue/PR has not been touched recently
Projects
None yet
Development

No branches or pull requests

3 participants