Strict-Transport-Security (HSTS)
Baseline: max-age=63072000; includeSubDomains; preload
Enforces HTTPS for all connections, preventing protocol downgrade attacks and cookie hijacking.
Reference for common HTTP headers and a builder to format header blocks. Covers Cache-Control, Content-Security-Policy, HSTS, CORS, Referrer-Policy, and more. Educational tool only — does not modify server responses.
Private-by-default, local browser execution. Generate raw blocks and server configs.
Copy-ready header blocks for raw HTTP, JavaScript fetch, nginx, Apache .htaccess, Express.js, and Vercel/Cloudflare JSON.
Important: This tool only generates header text for your server configuration files. It does NOT modify actual HTTP responses or connect to any server.
Testing your APIs with our JWT Decoder and URL Encoder often requires understanding these core security policies.
Baseline: max-age=63072000; includeSubDomains; preload
Enforces HTTPS for all connections, preventing protocol downgrade attacks and cookie hijacking.
Restricts which resources the browser may load and execute, preventing XSS and data-injection attacks by whitelisting trusted sources.
Example: default-src 'self'; script-src 'self'
Baseline: DENY or SAMEORIGIN
Defends against clickjacking by controlling whether the page can be embedded in frames or iframes by other sites.
Disables sensitive browser features such as camera and microphone access, e.g. camera=(), microphone=().
Reduces the attack surface by turning off features the site does not use.
Cache-Control: public, max-age=31536000, immutable for versioned static assets (CSS, JS, images) so browsers and CDNs cache them for up to a year. For non-versioned assets, use public, max-age=600, must-revalidate to balance freshness and caching.DENY, SAMEORIGIN) is the older header that controls framing. CSP frame-ancestors is the modern replacement and covers more sources. When both are present, modern browsers prioritize frame-ancestors. Use frame-ancestors 'self' or none in your CSP alongside X-Frame-Options: DENY for legacy browser support.Access-Control-Allow-Origin (e.g. * or a specific origin), Access-Control-Allow-Methods, Access-Control-Allow-Headers, and Access-Control-Max-Age to cache preflight responses. For credentialed requests, use a specific origin (not *) with Access-Control-Allow-Credentials: true.HTTP headers sit at the center of every request and response exchanged between a client and a server. They control caching, authentication, content negotiation, CORS, security policies, and connection behavior, yet their names, syntax, and default values are easy to forget under deadline pressure. The HTTP Headers Reference & Builder in DevPouch 2.0's web category combines a searchable reference of standard headers with a live builder that emits ready-to-use header blocks for fetch, cURL, Axios, and raw HTTP clients.
Instead of jumping between MDN pages, RFC documents, and scattered blog posts, developers can look up request, response, and entity headers in one place. Each entry covers header syntax, typical values, browser support, and common pitfalls such as case sensitivity and invalid directive combinations. The builder then lets you select headers, toggle options such as credentials or cache directives, and copy a complete header set directly into your code or API client.
Accurate headers reduce failed requests, improve caching efficiency, and close common security gaps. Use this reference and builder whenever you design APIs, integrate third-party services, or troubleshoot HTTP traffic across browsers, mobile clients, and origin servers.