On Sun, Feb 14, 2021 at 8:43 AM Roy Smith <r...@panix.com> wrote: > > I'm running a django app under toolforge. I see there's already a > > X_REQUEST_ID: e9ec1899b09244939d22c2387db3b75a > > header in the incoming request. That's totally cool, but I don't see it > documented in the toolforge docs. is that something the toolforge > infrastructure guarantees will be there?
It took some digging around to find a good answer for this question. It turns out that the ingress system that we are using for Toolforge's Kubernetes cluster is adding it. A request id header is added when an existing header is not found in the inbound request as it traverses the ingress. Brooke tracked down <https://github.com/kubernetes/ingress-nginx/issues/2546> upstream as a documented way that we could disable this default behavior if desired by the community or the Toolforge admins. Bryan -- Bryan Davis Technical Engagement Wikimedia Foundation Principal Software Engineer Boise, ID USA [[m:User:BDavis_(WMF)]] irc: bd808 _______________________________________________ Wikimedia Cloud Services mailing list Cloud@lists.wikimedia.org (formerly lab...@lists.wikimedia.org) https://lists.wikimedia.org/mailman/listinfo/cloud
