Do You Know These HTTP Status Codes As A Performance Test Engineer
By Sam Z // Saturday, June 14, 2014
Knowing the following application response status codes will help you to fix the issues promptly. Always we see these response status codes in performance testing tools Loadrunner, Jmeter and Neoload etc.
200 Status Codes:
Most the 200 status codes are success status codes. The server or application has successfully returned the requested page. Sometimes we validate the pages by using these status codes. The function that we use here is web_get_int_property in loadrunner.
300 Status Codes:
These Status Codes are re-directional codes. The page has moved to a different address, for example, if you type google.com the page will move to google.co.in this is redirection. There are two types: 301 redirection: The page you are looking no more exists and it is moved permanently to a different address. 302 Redirection: The page has been moved temporarily to a different address for many reasons like due to maintenance purposes. Due to 301 and 302 redirection sometimes we will not able to find correlation values in Loadrunner.
404 Status Code:
The page you are looking does not exist on this server. It's been removed or you might have entered a wrong URL.
500 Status Codes:
The server has problems in processing the request and these are mainly server errors and not with the request. For more response status codes, check out here HTTP Response Status Codes.