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
Describe the bug
I'm not entirely sure this is a bug however I'm not able to remove the Apollo-Expose-Query-Plan header from propagation unless I use remove.named.
To Reproduce
Steps to reproduce the behavior:
Setup router with header propagation with matching regex, propagate all request headers and then remove:
On the subgraph server print/log the headers passed and notice that Apollo-Expose-Query-Plan is being propagated to the subgraphs, also notice that x-amzn-mtls-clientcert-subject is not being propagated correctly.
Expected behavior
I don't expect Apollo-Expose-Query-Plan to be propagated to the subgraphs by default since it is a header that the router should consume. However using the matching expression should remove it.
Output
Inspect the headers passed to the subgraph server.
Desktop (please complete the following information):
OS: MacOS Sonoma
Version: 14.4.1 (23E224)
Additional context
I tried the following combinations:
Given what you've written here, this should certainly be working. Have you tried any variations of casing (e.g., all lower-case), to see if that helps? I'll mark this as a bug, but your continued investigation is certainly useful. Thanks!
Describe the bug
I'm not entirely sure this is a bug however I'm not able to remove the
Apollo-Expose-Query-Plan
header from propagation unless I useremove.named
.To Reproduce
Steps to reproduce the behavior:
matching
regex, propagate all request headers and then remove:Apollo-Expose-Query-Plan
is being propagated to the subgraphs, also notice thatx-amzn-mtls-clientcert-subject
is not being propagated correctly.Expected behavior
I don't expect
Apollo-Expose-Query-Plan
to be propagated to the subgraphs by default since it is a header that the router should consume. However using the matching expression should remove it.Output
Inspect the headers passed to the subgraph server.
Desktop (please complete the following information):
Additional context
I tried the following combinations:
With the above the header was propagated.
With the above the header was propagated.
With the above the header was propagated.
With the above the header was NOT propagated.
The text was updated successfully, but these errors were encountered: