fix(http): prevent multiple callbacks when a capture/match fails

[hassy]

Fixes #1542

[meetveera]

Hi @hassy - Good Morning. Thank you very much for fixing the problem. Now I am getting proper status codes for multiple redirects errors.
But again for some APIs it is still going on infinite loop. I double checked my API by executing it via postman and it is working fine there. When I did a little more digging and commented the below line from the snippet from my local machine that all my APIs started to work absolutely fine.

            // TODO: Handle the error properly with run hooks
            ee.emit('error', gotErr.code || gotErr.message);
           // return callback(gotErr, context); line 702 from engine_http.js
 });

Could you please take a look and see what exactly the problem is? I might be wrong but again commenting that line just worked for me and now all my apis are working fine via artillery run.

Thanks

[hassy]

@meetveera could you try the most recent release of Artillery to see if it fixes the issue.

[onematchfox]

@meetveera could you try the most recent release of Artillery to see if it fixes the issue.

Hi @hassy,

I'm also running into this issue - in the latest version 2.0.0-23. In my case it presents when looping over requests that are set to expect a specific status code (in one case a 403 and in another a 302). E.g.

- loop:
    - get:
        url: '/foo?bar={{ $loopElement }}'
        followRedirect: false
        expect:
          - statusCode: 302
  over: myVariable
- loop:
    - get:
        url: '/{{ $loopElement }}'
        expect:
          - statusCode: 403
  over: myVariable

Let me know if I should open a separate issue for this.