2026-04-24 · 1분 읽기
HTTP 응답 디버깅 체크리스트
상태 코드, 헤더, 페이로드 구조로 API 오류를 빠르게 분리합니다.
핵심 요점
- Check status code and Content-Type first before reading response body details.
- Reproduce with the same headers and query parameters to avoid false positives.
Fast triage flow
Start from response status, then inspect response headers. This quickly separates auth, validation, and upstream outages.
For 4xx responses, compare request headers and body shape against API docs before retrying.
For 5xx responses, preserve request IDs and timestamps so backend logs can be correlated.
Keep requests reproducible
Store the exact URL, query string, auth mode, and body used during debugging.
If your request includes dynamic fields (timestamps, nonces), pin test fixtures to reduce noise.
자주 묻는 질문
Why do I still get 401 after adding a token?
Double-check Authorization format and whether the upstream expects Bearer, Basic, or signed cookies.
What should I inspect for 415 or 422 errors?
Verify Content-Type and payload schema. Validate JSON locally before sending the request.