> For example, it mentions adding instrumentation caused the issue, but no details as to how why they'd need to remove headers They probably don't need to at a

> For example, it mentions adding instrumentation caused the issue, but no details as to how why they'd need to remove headers They probably don't need to at all, but I can think or several ways it might unintentionally happen. Perhaps someone chose to implement the modification as “separate headers & body, modify headers, put the request back together” and something went wrong that made the putting-back-together fail quietly (so the now malformed request passes to the next part without an exception being raised) or not get called at all in some circumstances. Alternately a badly coded routine to remove a header, perhaps the instrumentation information after the point in the processes it is no longer useful, maybe removed more than it should. How such things get past a code review without someone suggesting a less error-prone method might be a question that gets asked in the internal investigation. I assume somewhere like CF has many checks between initial code modifications and things dropping into production, unless they've really taken “fail fast” to heart!