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
Hi,
we configured the opentracing plugin on nginx 1.19.8 and all works fine, but we noticed that all requests had the header X-B3-Flags set to 0 and our backend API GW logged an error if this header has a value different from "1".
We tried to use proxy_set_header config to override this value but it's not possible to remove the header sent by nginx.
Is is possible to avoid the forward of the "x-b3-flags: 0" and omit it if necessary via config file?
Thanks,
Marcello
The text was updated successfully, but these errors were encountered:
@miry we noticed that is a part of the zipkin-cpp-opentracing module and it forwards all requests with the x-b3-flags to zero, but on nginx side you can't override it to 0 or 1 in case of debug.
Hi,
we configured the opentracing plugin on nginx 1.19.8 and all works fine, but we noticed that all requests had the header X-B3-Flags set to 0 and our backend API GW logged an error if this header has a value different from "1".
We tried to use proxy_set_header config to override this value but it's not possible to remove the header sent by nginx.
Is is possible to avoid the forward of the "x-b3-flags: 0" and omit it if necessary via config file?
Thanks,
Marcello
The text was updated successfully, but these errors were encountered: