Synopsis
Display HTTP request and response headers for a specific network request or the main document.
bdg network headers [id] [options]
Description
The network headers command displays both request and response HTTP headers for a specific network request.
Without a request ID, shows headers for the current main document (the HTML page). If the page has navigated since the session started, this will be the latest navigation, not the original URL.
Use request IDs from bdg network list or bdg peek --network output to inspect specific requests.
Arguments
Request ID from network list or peek --network output.If omitted, displays headers for the current main HTML document.
Options
Filter to a specific header name (case-insensitive). Shows only this header from both request and response.Example: --header content-type
Output results in JSON format for programmatic consumption.
Human-readable (default)
Network Request Headers
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
URL: https://example.com/api/users
Response Headers:
cache-control: max-age=3600, public
content-encoding: gzip
content-type: application/json; charset=utf-8
date: Thu, 05 Mar 2026 14:30:22 GMT
etag: "abc123"
server: nginx/1.21.0
set-cookie: session=xyz; HttpOnly; Secure
x-cache: HIT
x-ratelimit-limit: 1000
x-ratelimit-remaining: 999
Request Headers:
accept: application/json
accept-encoding: gzip, deflate, br
authorization: Bearer eyJ...
cache-control: no-cache
user-agent: Mozilla/5.0 ...
x-request-id: req-12345
Request ID: 004
bdg network headers 004 --header content-type
Network Request Headers
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
URL: https://example.com/api/users
Response Headers:
content-type: application/json; charset=utf-8
Request Headers:
Request ID: 004
{
"version": "1.2.3",
"success": true,
"data": {
"url": "https://example.com/api/users",
"requestId": "004",
"requestHeaders": {
"accept": "application/json",
"accept-encoding": "gzip, deflate, br",
"authorization": "Bearer eyJ...",
"cache-control": "no-cache",
"user-agent": "Mozilla/5.0 ...",
"x-request-id": "req-12345"
},
"responseHeaders": {
"cache-control": "max-age=3600, public",
"content-encoding": "gzip",
"content-type": "application/json; charset=utf-8",
"date": "Thu, 05 Mar 2026 14:30:22 GMT",
"etag": "\"abc123\"",
"server": "nginx/1.21.0",
"set-cookie": "session=xyz; HttpOnly; Secure",
"x-cache": "HIT",
"x-ratelimit-limit": "1000",
"x-ratelimit-remaining": "999"
}
}
}
Examples
Show main document headers
# Get request ID from list
bdg network list --filter "domain:api.*"
# Then inspect headers
bdg network headers 004
bdg network headers 004 --header content-type
bdg network headers 004 --header authorization
bdg network headers 004 --header cache-control
Get headers as JSON and parse
bdg network headers 004 --json | jq '.data.responseHeaders."content-type"'
bdg network headers 004 --json | jq '.data.responseHeaders | {limit: ."x-ratelimit-limit", remaining: ."x-ratelimit-remaining"}'
bdg network headers --header set-cookie
Use Cases
Debug CORS issues
# Check CORS headers on API request
bdg network list --filter "domain:api.*"
bdg network headers 004 --header access-control-allow-origin
Verify authentication
# Check if Authorization header is being sent
bdg network headers 004 --header authorization
Inspect caching behavior
# Check cache-related headers
bdg network headers 004 --json | jq '.data.responseHeaders | {"cache-control", "etag", "x-cache"}'
Monitor rate limits
# Extract rate limit info
bdg network headers 004 --json | jq -r '.data.responseHeaders | "Limit: \(."x-ratelimit-limit"), Remaining: \(."x-ratelimit-remaining")"'
Check compression
# Verify content-encoding
bdg network headers --header content-encoding
Security audit
# Check security headers
bdg network headers --json | jq '.data.responseHeaders | {"strict-transport-security", "content-security-policy", "x-frame-options"}'
Exit Codes
Headers retrieved successfully
Request ID not found, or no network requests captured yet
Failed to connect to daemon
Companion Commands
network document
Alias for network headers without an ID - shows main document headers:
bdg network document [--header <name>] [--json]
bdg network headers [--header <name>] [--json]
Tips
Find Request IDs: Use bdg network list to find request IDs:bdg network list --filter "domain:api.*"
# [004] 200 GET XHR 2.1 KB https://api.example.com/users
bdg network headers 004
Main Document: Without an ID, network headers shows the current main document. If the page navigated, this is the latest navigation:bdg example.com # Start session
# ... page redirects to example.com/login
bdg network headers # Shows headers for /login (current page)
Case-Insensitive Filtering: The --header option is case-insensitive:bdg network headers --header CONTENT-TYPE
bdg network headers --header content-type
# Both work identically
Request headers may contain sensitive data like authorization tokens. Be careful when logging or sharing output.
See Also
- network list - List network requests to find IDs
- network getCookies - List cookies (alternative to Set-Cookie header)
- peek - Quick session overview including recent requests
- details - Get full details for a network request
