# Enabling headers in Live calls

_[New in v1.0.0](/release-notes/linkerd-dashboard/v1.0.0/)_

By default, Live calls show request details without HTTP headers. This guide
shows you how to include request headers, response headers, and trailers, and
how to choose which headers are shown.

> [!WARNING]
> Headers can contain sensitive values, such as credentials
> and session cookies. Anyone who can use the dashboard can see
> them.

## Prerequisites

- The [Linkerd dashboard](/linkerd-dashboard/getting-started/) installed on your cluster
- [Live calls enabled](/linkerd-dashboard/guides/enabling-live-calls/)

## Enable headers

Set the dashboard's `tapHeadersEnabled` value:

```bash
helm upgrade -n monitoring linkerd-dashboard \
  oci://ghcr.io/buoyantio/charts/linkerd-dashboard --reuse-values \
  --set tapHeadersEnabled=true
```

After the dashboard has restarted to pick up the new setting, Live calls will
show the headers in the proxy's default allow list: `Accept`, `Content-Length`,
`Content-Type`, `Date`, `Host`, `Last-Modified`, `Server`, and `User-Agent`.

## Choose which headers are shown

The allow list is applied by each workload's Linkerd proxy. To show a specific
set of headers, set the `tap.buoyant.io/headers-allow` annotation to a
comma-separated list of header names.

To set it for every workload in a namespace, annotate the namespace:

```bash
kubectl annotate namespace <namespace> \
  tap.buoyant.io/headers-allow='Accept,Content-Length,User-Agent'
```

To set it for one workload, add it to the workload's pod template. A workload's
annotation takes precedence over its namespace's:

```yaml
spec:
  template:
    metadata:
      annotations:
        tap.buoyant.io/headers-allow: "Accept,Content-Length,User-Agent"
```

The annotation is applied when the proxy is injected, so restart your workloads
for the change to take effect. For example:

```bash
kubectl -n <namespace> rollout restart deployment/<name>
```

> [!NOTE]
> Setting the annotation to an empty string (`""`) stops all
> headers from being shown. To go back to the default allow list, remove the
> annotation. An invalid value is ignored, and the proxy injector logs a warning
> starting with `Invalid value for tap.buoyant.io/headers-allow`.

## Disable headers

To turn headers off again, set `tapHeadersEnabled` to `false` the same way.
