{"source":"semconv","version":"1.44.0","attribute":{"id":"http.response.header","type":"template[string[]]","stability":"stable","brief":"HTTP response headers, `<key>` being the normalized HTTP Header name (lowercase), the value being the header values.","note":"Instrumentations SHOULD require an explicit configuration of which headers are to be captured.\nIncluding all response headers can be a security risk - explicit configuration helps avoid leaking sensitive information.\n\nUsers MAY explicitly configure instrumentations to capture them even though it is not recommended.\n\nThe attribute value MUST consist of either multiple header values as an array of strings\nor a single-item array containing a possibly comma-concatenated string, depending on the way\nthe HTTP library provides access to headers.\n\nExamples:\n\n- A header `Content-Type: application/json` header SHOULD be recorded as the `http.request.response.content-type`\n  attribute with value `[\"application/json\"]`.\n- A header `My-custom-header: abc, def` header SHOULD be recorded as the `http.response.header.my-custom-header`\n  attribute with value `[\"abc\", \"def\"]` or `[\"abc, def\"]` depending on the HTTP library.","examples":["[\"application/json\"]","[\"abc\",\"def\"]"],"namespace":"http","definedIn":"model/http/registry.yaml","usedBy":[{"groupId":"span.http.client","groupType":"span","requirementLevel":"opt_in"},{"groupId":"span.http.server","groupType":"span","requirementLevel":"opt_in"}]},"history":[{"version":"1.30.0","publishedAt":"2025-01-24T19:11:42Z","kind":"first-seen","detail":"Already present at v1.30.0, the oldest release tracked here (stable)."}],"replaces":[]}