Output Formatting and Redirection

This rule applies to files matching the patterns above.

# Output Formatting and Redirection

## Rule
Use HTTPie's --print flag to control output sections. Use --body for piping to other tools. Use --download for binary files. Always combine with jq for JSON processing in scripts.

## Print Flag Options
| Flag | Sections | Use Case |
|------|----------|----------|
| `--print=H` | Request headers | Debug request |
| `--print=B` | Request body | Verify payload |
| `--print=h` | Response headers | Check status/headers |
| `--print=b` | Response body | Pipe to jq/processing |
| `--print=hb` | Response headers + body | Full response |
| `--print=HhBb` | Everything | Full debugging |

## Good Examples
```bash
# Extract response body for piping to jq
http --print=b GET api.example.com/users | jq '.[].name'

# Save response to file
http --print=b --output users.json GET api.example.com/users

# Download binary files properly
http --download GET api.example.com/reports/q4.pdf

# Debug mode — see everything
http --print=HhBb POST api.example.com/orders name="Widget"

# Check response headers only
http --print=h HEAD api.example.com/health
```

## Bad Examples
```bash
# BAD: Full output when piping — headers corrupt the data
http GET api.example.com/users | jq .
# Includes colored headers before JSON — jq fails
# Use: http --print=b GET api.example.com/users | jq .

# BAD: Saving binary with default output
http GET api.example.com/file.zip > file.zip
# Use: http --download GET api.example.com/file.zip
```

## Enforcement
- Always use --print=b when piping to other tools
- Use --download for binary content
- Use --check-status in scripts to fail on HTTP errors