# Capture a browser request for diagnosis

A browser network archive can help explain a failed Playground request by preserving its URL, status and timing. Open the browser's developer tools, select the Network panel, clear unrelated requests and reproduce the issue once. Inspect the SQL request and its response before exporting the browser's network archive.

For Coordinator DB, useful details include the selected database, response status, `X-Coordinator-Query-Id`, `X-Coordinator-Exception-Code` and the response text. An HTTP SQL error commonly uses status 400; authentication and admission failures use different statuses. The exact error is more useful than a screenshot showing only a generic failure.

Before sharing an archive, remove Authorization headers, passwords, Bearer keys, SQL literals containing private data and returned rows. Inspect the exported file itself: a browser's display of hidden header values does not guarantee they were excluded from an export.

Browser requests must satisfy the documented Origin and Host rules, and the server does not emit CORS headers. If command-line requests succeed while browser requests fail, compare those request details directly rather than changing SQL at random.

See [HTTP requests and responses](https://coordinatordb.com/docs/concepts/features/interfaces/http) and [authentication](https://coordinatordb.com/docs/concepts/features/security).