-
Notifications
You must be signed in to change notification settings - Fork 10.7k
Serialize response context as a response header #5928
Copy link
Copy link
Closed
Labels
acceptedThis issue has completed "acceptance" testing (including accessibility)This issue has completed "acceptance" testing (including accessibility)area-hostingIncludes HostingIncludes Hostingarea-networkingIncludes servers, yarp, json patch, bedrock, websockets, http client factory, and http abstractionsIncludes servers, yarp, json patch, bedrock, websockets, http client factory, and http abstractionsenhancementThis issue represents an ask for new feature or an enhancement to an existing oneThis issue represents an ask for new feature or an enhancement to an existing one
Milestone
Description
Metadata
Metadata
Assignees
Labels
acceptedThis issue has completed "acceptance" testing (including accessibility)This issue has completed "acceptance" testing (including accessibility)area-hostingIncludes HostingIncludes Hostingarea-networkingIncludes servers, yarp, json patch, bedrock, websockets, http client factory, and http abstractionsIncludes servers, yarp, json patch, bedrock, websockets, http client factory, and http abstractionsenhancementThis issue represents an ask for new feature or an enhancement to an existing oneThis issue represents an ask for new feature or an enhancement to an existing one
Type
Fields
Give feedbackNo fields configured for issues without a type.
Motivation
In distributed tracing scenarios it is not uncommon to return extra context as a response headers when possible. DiagnosticsSource Acitvity should implement API that will allow to set the response context. Fields populated by this API should be serialized as http response headers.
CC: @seth-capistron, @vancem, @jacpull, @lmolkova, @glennc, @davidfowl