—
—
RFC 6266 · RFC 8187
See what that download header actually says.
Paste one Content-Disposition response-header value. Inspect syntax, filename precedence, extended-value decoding, and filesystem-name warnings without sending the value anywhere.
02 / Standards report
Inspection result
Waiting for inspection.
Recovery is unknown. This report does not predict how a specific browser will recover from invalid or unsupported input.
—
—
Parsed parameters
| Name | Wire value | Decoded | Reading |
|---|
Errors, support boundaries, and name warnings
Reconstructed example
Conservative ASCII fallback plus UTF-8 filename*. This is a standards-shaped header example, not proof that the downloaded payload or name is safe.
No reconstructed example available
It means the inspected syntax fits this profile. It does not certify server behavior, payload safety, or a recipient's filesystem choices.
Legacy charsets, unknown charsets, continuations, and non-ASCII regular values are surfaced instead of guessed.
When both parameters are valid and decodable, the RFC 8187 extended value takes precedence over the regular fallback.