@@ -86,7 +86,6 @@ struct datadog_main_conf_t {
86
86
// (e.g. before the first `server` block, before the first `access_log`
87
87
// directive).
88
88
bool are_log_formats_defined;
89
- std::vector<std::string_view> span_context_keys;
90
89
// This module automates the forwarding of the environment variables in
91
90
// `TracingLibrary::environment_variable_names()`. Rather than injecting
92
91
// `env` directives into the configuration, or mucking around with the core
@@ -109,13 +108,6 @@ struct datadog_main_conf_t {
109
108
std::optional<configured_value_t > environment;
110
109
// `agent_url` is set by the `datadog_agent_url` directive.
111
110
std::optional<configured_value_t > agent_url;
112
- // `is_sampling_delegation_response_header_added` is whether we have added an
113
- // `add_header` directive before the first `server` block within the
114
- // configuration. The directive is used to include the
115
- // X-Datadog-Trace-Sampling-Decision response header when the client
116
- // requested trace sampling delegation. This `bool` ensures that the
117
- // directive is not added more than once.
118
- bool is_sampling_delegation_response_header_added;
119
111
120
112
#ifdef WITH_WAF
121
113
// DD_APPSEC_ENABLED
@@ -196,10 +188,6 @@ struct datadog_loc_conf_t {
196
188
NgxScript loc_resource_name_script;
197
189
ngx_flag_t trust_incoming_span = NGX_CONF_UNSET;
198
190
ngx_array_t *tags;
199
- // `response_info_script` is a script containing variables that refer
200
- // to HTTP response headers. This is used by sampling delegation to
201
- // retrieve the sampling decision made by an upstream service.
202
- NgxScript response_info_script;
203
191
// `proxy_directive` is the name of the configuration directive used to proxy
204
192
// requests at this location, i.e. `proxy_pass`, `grpc_pass`, or
205
193
// `fastcgi_pass`. If this location does not have such a directive directly
@@ -226,15 +214,6 @@ struct datadog_loc_conf_t {
226
214
// `sampling_delegation_directive` is the source location of the
227
215
// `datadog_delegate_sampling` directive that applies this location, if any.
228
216
conf_directive_source_location_t sampling_delegation_directive;
229
- // `is_sampling_delegation_response_header_added` is whether we have added an
230
- // `add_header` directive before the first user-specified `add_header`
231
- // directive within this server/location block. The directive is used to
232
- // include the X-Datadog-Trace-Sampling-Decision response header when the
233
- // client requested trace sampling delegation. The inserted `add_header` is
234
- // necessary only if there are user-defined `add_header` directives at the
235
- // same level; if not, then the `add_header` is inherited from the `http`
236
- // block.
237
- bool is_sampling_delegation_response_header_added;
238
217
// `block_type` is the name of the kind of configuration block we're in, e.g.
239
218
// "http", "server", "location", or "if". `block_type` is used by some
240
219
// configuration directives to alter their behavior based on the current
0 commit comments