Recording request headers needed to reproduce a failure
A reproducible request report needs more than a URL. Keep the relevant request conditions, but remove secrets before sharing evidence.
Capture useful request context
Record the method, timestamp, requested URL and non-sensitive headers that may distinguish the failing request. Note whether the request was anonymous. Preserve the response status, destination and a safe excerpt of the body. Do not paste cookies, authorization values, private query tokens or customer information into tickets or public reports.
Minimize the reproducer
Compare a sanitized request with the original behavior. If removing a header changes the result, identify that difference without exposing its secret value. Ask the responsible operator to reproduce sensitive cases in an authorized environment. The goal is a small, repeatable description of the defect, not a full export of someone’s browsing session.
Source guidance
Use the website analyzer to collect a starting set of observations, then verify the specific evidence described above.Frequently Asked Questions
What if the failure requires a private session?
Describe the required access state and provide non-sensitive observations. An authorized operator can reproduce it without distributing credentials in the report.