-
-
Notifications
You must be signed in to change notification settings - Fork 744
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
Access to stitched http response headers (e.g. Set-Cookie) #679
Comments
Sorry for letting you wait ... I will look into this tomorrow. |
The In schema stitching this property bag can basically used to store anything from a remote schema. We will also add a client handler now that can be injected. So basically by injecting a client handler as a service you can now transfer any kind of data into this dictionary. The stitching middleware will copy the context data in the scoped resolver context data so that one can access this one in the stitching layer. |
public interface IHttpQueryRequestInterceptor
{
Task OnReceivedResultAsync(
IHttpQueryRequest request,
HttpResponseMessage response,
IQueryResult result);
} |
this one is now done and included in preview.35. |
Hi @michaelstaib , we are trying to implement the same as mentioned above in our project to access the remote schema response headers in Gateway. But couldnt use "IHttpQueryRequestInterceptor" interface. what would be the HC namespace to access this interface ? |
Is your feature request related to a problem? Please describe.
Some stitched endpoints set response cookies via the
Set-Cookie
header. I need to "proxy" those headers back to the original http request so the client can get them set. In some cases I may need to modify those values (e.g. modify a domain, if set).Describe the solution you'd like
A clear extension point for intercepting stitched-schema-responses with access to the resolver context.
Describe alternatives you've considered
Well, not using cookies. That works fine sometimes, depending on how much control we have over the endpoint we're stitching. But I could envision wanting to interact with other reasons to access headers (logging, metrics, etc).
The text was updated successfully, but these errors were encountered: