You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In order to support concurrent usage of mirrord on the same service in e.g. a staging cluster, we need to let users filter requests routed to them by header.
For example, when running mirrord-layer with FILTER_INCLUDE="mirrord-user: eyal", only requests with the specified header would be routed by the agent to the layer. Extrapolate to FILTER_EXCLUDE.
Change existing stealer to be global per agent, rather than multiple stealers per agent (one per subscribed layer)
Develop the Filter component - this component will know to receive raw HTTP traffic and a collection of filters, and determine whether the traffic answers one or more of the filter conditions. If it answers more than one filter conditions, just use the first one.
Change the Stealer component to use the Filter component.
Implement subscription with filters by configuration in the layer.
The text was updated successfully, but these errors were encountered:
#290
- Introduce Filtered subscriptions to protocol and stealer api.
- Interface with HttpFilterManager.
- Handle filtered subscriptions in stealer.
- Handle new incoming connections on filtered ports.
- Forward stolen requests to appropriate client (stealer client=layer).
- Forward responses to stolen requests from layer back to browser.
Co-authored-by: t4lz <[email protected]>
In order to support concurrent usage of mirrord on the same service in e.g. a staging cluster, we need to let users filter requests routed to them by header.
For example, when running mirrord-layer with FILTER_INCLUDE="mirrord-user: eyal", only requests with the specified header would be routed by the agent to the layer. Extrapolate to FILTER_EXCLUDE.
Architecture here.
Subtasks:
The text was updated successfully, but these errors were encountered: