Terminology Index

Glossary

1801 terms

Open concept maps

Showing 1313-1344 of 1801 terms

R
32

Response

An HTTP message returned by a server to a client, carrying a status, headers, and content. Defenders read responses to understand application behavior and to spot leakage or anomalies in server replies.

An HTTP response answers a request with a status code, headers, and usually a body. For defenders, responses matter for understanding application behavior and security: status codes hint at failures and forced-browsing attempts, headers carry security-relevant settings (CSP, HSTS, cookies), and content can leak sensitive data if not handled carefully. Reading responses in logs and proxies is part of foundational web defense, paired with reading requests.

Introduced in: Defensive Web Fundamentals

Examples

  • Inspecting a response's status code to interpret what happened.
  • Checking security-related headers like CSP and HSTS in responses.
  • Spotting unexpected sensitive data in a response body.

No related terms linked yet.