🛰 POCs to demonstrate and verify features required for implementing an in-proxy authorization cache🛰️
Explore the docs »
Several POCs to demonstrate and verify features required for implementing an in-proxy local cache.
Note: Please refer to the individual POC documentation for more information regarding each of the POCs.
- Rate limit header POC
- Handling rate limit logic inside a HTTP filter with the help of shared data (cache) and adding rate limit headers from the response path.
- Set dynamic metadata POC
- Currently setting up dynamic metadata is not support in proxy-wasm-rust-sdk. (#81). As a workaround headers can be added from the request path and then those headers can be converted to dynamic metadata using envoy header to metadata filter.
- In proxy cache implementation using shared data, singleton service and HTTP filter
- This is done as a part of the GSoC proposal and it uses shared data to store the cache. And it uses singleton service to flush the cache to a remote service and update the local cache using the response of that request. Authorization and rate limiting is performed from the HTTP filter per each HTTP call using the cache stored in the shared data. This POC is in my personal github account.