Skip to content

Document custom secret header bindings and response redaction - #26715

Open
dvdksn wants to merge 7 commits into
mainfrom
docsflow/docs-1hen7
Open

dvdksn wants to merge 7 commits into
mainfrom
docsflow/docs-1hen7

Conversation

@dvdksn

@dvdksn dvdksn commented Nov 20, 2026

Copy link
Copy Markdown
Contributor

Explain how to bind local custom secrets to request headers and configure secret.custom.defaultHeaders. Add migration guidance for existing secrets, the eight-character minimum, and response-redaction limits so users can update their authentication setup.

Validation: scoped Markdown and Vale checks passed. Command examples were reviewed against source and tests; runtime verification was unavailable.

Custom secret guidance did not explain which headers receive credentials. Document explicit and default header bindings, migration steps, and the limits of response redaction.
@netlify

netlify Bot commented Nov 20, 2026 •

Copy link
Copy Markdown

✅ Deploy Preview for docsdocker ready!

Name Link
🔨 Latest commit 6094b7f
🔍 Latest deploy log https://app.netlify.com/projects/docsdocker/deploys/6b00764271cfc358699ca7d8
😎 Deploy Preview https://deploy-preview-26715--docsdocker.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@dvdksn dvdksn added this to the sbx/v0.55.0 milestone Nov 20, 2026
Describe custom secrets in terms of current behavior and link to the settings reference for default headers. Remove migration details and format rejected headers as a list.
An older running daemon cannot apply default headers to custom secrets. Document the API requirement, the effect of credential synchronization, and the restart needed after an upgrade.
The header configuration guide interrupted normal usage with daemon compatibility details. Move recovery steps to troubleshooting, anchored to the reported error, and omit internal API versions.
The response filtering guidance leaves readers to interpret its limits and the meaning of a WebSocket upgrade. Explain when filtering applies, what it recognizes, and how its limits affect clients.
The custom secret troubleshooting section describes a client and daemon version mismatch after an upgrade. Remove this recovery scenario from the guide because upgrades restart the daemon.
@dvdksn
dvdksn marked this pull request as ready for review November 20, 2026 15:38
@dvdksn
dvdksn requested review from a team and kevin-docker November 20, 2026 15:38
Explain how header defaults and minimum length affect existing secrets, align HTTPS substitution wording, and shorten the proxy-controlled header reference.
dvdksn added a commit that referenced this pull request Nov 20, 2026
Leave the shared custom-secret paragraph to PR #26715 so the HTTPS and header-binding updates can merge without overwriting each other. The HTTPS requirement remains documented in the injection overview.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant