201 and 204 responses treated as errors when running JMeter .jmx file with HTTP Samplers.

[akozmic-prisidio]

Describe the bug Using a Jmeter .jmx file that has HTTP samplers and running on AWS Distributed Load Testing, it appears that the reports are treating 201 and 204 responses as errors.

To Reproduce Create a JMeter test plan .jmx file with at least 1 HTTP Sampler that makes a request that expects a 201 response (such as a POST to create an object in a REST API). Deploy the AWS Distributed Load Testing stack, login, and run the .jmx. Note that the 201 is reported as an error (see screenshot). The same occurs for a 204 (such as a DELETE to delete an object in a REST API).

Expected behavior I would expect that any 2xx error code would be treated as successful. Or at least that the developer would have the ability to specify the expected errorCodes.

Please complete the following information about the solution:

• [x] Version: [e.g. v1.1.0] 2.0.0
• [x] Region: [e.g. us-east-1] us-east-1
• [x] Was the solution modified from the version published on this repository? No
• [x] If the answer to the previous question was yes, are the changes available on GitHub?
• [x] Have you checked your service quotas for the sevices this solution uses? N/A
• [x] Were there any errors in the CloudWatch Logs? No

Screenshots

[gattasrikanth]

Thankyou for the feedback. We will add this to our backlog items.

[devopeak]

Unsure if this is the place to raise this, but it seems related. A 302 is also treated as an error when it may be an expected redirection.

[emcfins]

This is the right place! Thanks for your feedback, we will add it to the list.