HTTP Header Builder
Build a tidy header block from key/value lines, with common security headers ready to add.
HTTP Header Builder
Type one Name: value pair per line. Names are validated, the last value wins for a repeated name, and ticked security headers are added only when you have not set them yourself. The result is a clean block you can paste into a request or a server config.
Header block
History tool ini
Data terakhir yang pernah kamu isi di tool ini, tersimpan hanya di device/browser ini.
Save what you type here, in this browser? Your work would go into this browser's local storage, so a refresh or a trip to another tool does not wipe it. You also get a short list of previous entries under the form, each one restorable with a click. Nothing is ever uploaded, and there is no account.
Being straight about the trade-off: anything kept there can be read by anyone who can use this browser profile, and by any script that later runs on this site. A tool page can hold a private key, a password or a signed token. Saving is convenient; it is not private.
About this tool
A small workbench for building a header block. Type one Name: value pair per line, tick any common security headers you want added, and the page validates the names, keeps the last value for a repeat and emits a clean block ready to paste into a request or a server config.
Questions
- What makes a valid header name?
- A header name is an HTTP token: letters, digits and a small set of symbols, with no spaces or colons. The builder checks each name against that rule and reports any line it cannot use instead of guessing what you meant.
- What happens if I list the same header twice?
- The last value wins. That matches how most tools and servers resolve a duplicated field, and it means you can put a placeholder near the top and override it further down without editing the earlier line.
- Which security headers can I add?
- HSTS, X-Content-Type-Options, X-Frame-Options, Referrer-Policy, a starter Content-Security-Policy, Permissions-Policy and a no-store Cache-Control. They are added only when you have not already set that header yourself, so your own value is never overwritten.
- Does the page send the headers anywhere?
- No. It is a text builder: the input is parsed and the output is written back into the page. Nothing is transmitted, which is safe even when the block contains an Authorization value.