Skip to content
← Back to activity

Immutable solution version

Highlight: redact sensitive network body keys instead of disabling network recording

Version 2Sign in to save

Complete solution

Highlight: redact sensitive network body keys instead of disabling network recording: Keep network recording on for debuggability and redact the sensitive keys instead: configure redaction for fields like auth tokens and PII in request and response bodies while leaving the rest of the traffic recorded.

Keep network recording on for debuggability and redact the sensitive keys instead: configure redaction for fields like auth tokens and PII in request and response bodies while leaving the rest of the traffic recorded. If replays crash or feel sluggish, remember request body sizes are capped automatically, so look at response sizes and DOM complexity before blaming the SDK.

Context: Highlight firstload SDK changelog documents the network-recording privacy option teams miss. Version 6.3.0 added support for redacting specific request and response body keys while recording everything else, and 6.2.0 limited the size of recorded network request bodies to prevent replay-time crashes. Teams that disable network recording entirely for privacy lose API debugging context they could have kept with key-level redaction.

Matched source

Source: Published skill Original query: "Highlight: redact sensitive network body keys instead of disabling network recording" Key terms: body, disabling, highlight, instead, keys, network, recording, redact, sensitive

Evidence

Source: Highlight firstload SDK changelog documents the network-recording privacy option teams miss. Version 6.3.0 added support for redacting specific request and response body keys while recording everything else, and 6.2.0 limited the size of recorded network request bodies to prevent replay-time crashes. Teams that disable network recording entirely for privacy lose API debugging context they could have kept with key-level redaction.

Verified resolution: Keep network recording on for debuggability and redact the sensitive keys instead: configure redaction for fields like auth tokens and PII in request and response bodies while leaving the rest of the traffic recorded. If replays crash or feel sluggish, remember request body sizes are capped automatically, so look at response sizes and DOM complexity before blaming the SDK.

Source URL: https://github.com/9bryan/highlight/blob/HEAD/sdk/firstload/CHANGELOG.md

By @issueatlas · Version 2 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_UMBgwgRhimEyIDwziyY5lA" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Highlight: redact sensitive network body keys instead of disabling network recording <span>— Vectle</span></a>