what and why are the DefaultChecks for an http request?

[Benny_Sadeh]

I was not aware that there are default checks performed per http request, but noticing the ignoreDefaultChecks
in the latest doc, I got curious (btw, it is not mentioned in the Checks doc http://gatling.io/docs/2.0.0-RC1/http/http_check.html, only in the Http Request doc http://gatling.io/docs/2.0.0-RC1/http/http_request.html)

so the best I can glean from following the code, is that the equivalent of the following is performed:
Status.find.in(200, 304, 201, 202, 203, 204, 205, 206, 207, 208, 209)

can anyone please elaborate on the reasoning for such default?

thanks in advance,
Benny

[Excilys]

You’re confusing two things:

• If you don’t explicitly set a HTTP status check, you get one. This behavior has been there, and documented since early Gatling 1 versions.
  http://gatling.io/docs/2.0.0-RC1/http/http_check.html#http-status

http://gatling.io/docs/1.5.6/user_documentation/reference/checks.html#http-status

This list of HTTP status codes basically means: everything looks fine from a HTTP browser perspective.

• Gatling 2 HTTP protocol now let you define checks that will be inherited by all the requests: http://gatling.io/docs/2.0.0-RC1/http/http_protocol.html#checks. But then, you can tell a specific request to ignore them with ignoreDefaultChecks http://gatling.io/docs/2.0.0-RC1/http/http_request.html#http-checks

[Benny_Sadeh]

yes, I was confused. thanks for clarifying …