-
Notifications
You must be signed in to change notification settings - Fork 36
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
Variable from interceptor to originSelector #35
Comments
This is really a good question. I think setting the origin selector to return request options can solve the problem. |
I think we could resolve the origin server before the interceptors kick-in and then it would be exposed in the ProxyContext and can be overriden, or something like that . |
sometimes the ProxyContext is not available for a resolution, e.g in the WebSocket case, so we need to come with an interface that provides similar info for this case |
Sometimes we might want to assign a variable inside an interceptor that will help the origin selector to decide the actual origin. What is the optimal way to do these as of now. I searched and could not find anything
The text was updated successfully, but these errors were encountered: