0% found this document useful (0 votes)
4 views1 page

API Testing Styled

The document outlines HTTP status codes, categorizing them into 400 series errors (client-side issues) and 500 series errors (server-side issues). It details specific errors such as 400 Bad Request, 401 Unauthorized, and 500 Internal Server Error, along with their causes and implications. The key difference highlighted is that 4xx errors indicate client issues while 5xx errors indicate server issues.

Uploaded by

isfaque12
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
4 views1 page

API Testing Styled

The document outlines HTTP status codes, categorizing them into 400 series errors (client-side issues) and 500 series errors (server-side issues). It details specific errors such as 400 Bad Request, 401 Unauthorized, and 500 Internal Server Error, along with their causes and implications. The key difference highlighted is that 4xx errors indicate client issues while 5xx errors indicate server issues.

Uploaded by

isfaque12
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

API Testing - HTTP Status Codes

400 Series Errors (Client Side)


These errors occur due to issues in the client request.

400 Bad Request


Invalid syntax or missing parameters.

401 Unauthorized
Authentication required or failed.

403 Forbidden
Permission denied.

404 Not Found


Resource not found.

500 Series Errors (Server Side)


These errors occur when the server fails to process a valid request.

500 Internal Server Error


Generic server failure. Causes: crash, DB issues. Testing: validate request, log, report.

502 Bad Gateway


Invalid response from another server. Causes: microservice failure.

503 Service Unavailable


Server temporarily down due to maintenance or overload.

504 Gateway Timeout


Server took too long to respond. Causes: slow backend.

Key Difference
4xx → Client Issue | 5xx → Server Issue

You might also like