-
Notifications
You must be signed in to change notification settings - Fork 107
Unlike in other SDKs, there is no link between RootContext
and HttpContext
/ StreamContext
#6
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
Comments
I'm also trying to understand how to solve this problem, and pass configuration to my HttpContext. |
I just wasted a bunch of time on this. If the callbacks would accept closures with environment captures, this wouldn't be an issue |
…llow `RootContext` propagate configuration into `HttpContext`/`StreamContext` (proxy-wasm#6)
I am also trying to reading configuration and pass it into |
Fixes #6. Signed-off-by: Daniel Grimm <dgrimm@redhat.com>
Summary
RootContext
andHttpContext
, it's not possible to to apply toHttpContext
configuration that was set in theRootContext
duringproxy_on_configure
HttpContext
gets created by a standalone factory function rather than byRootContext
?The text was updated successfully, but these errors were encountered: