Skip to content

Artillery's followRedirect: true doesn't properly handle POST→GET redirect conversion #3661

@amit-saini-tx

Description

@amit-saini-tx

We can see that Artillery's followRedirect: true with POST requests doesn't work correctly - it makes another POST instead of GET to the redirect URL, which causes the 403 error.

Version info:

<2.0.26>

I expected to see this happen:

It should make a GET call for the redirects calls and expected status code is 200

Instead, this happened:

Its making a POST call for the redirect call and ending up with error code 403

Sample YAML :

- post:
          url: "{{secureBaseUrl}}/checkout/offer-external"
          name: "POST_add_subscription_to_cart"
          form:
            skuCode: "{{ sku }}"
            pkey: "croDefaultPromo"
          followRedirect: true
          beforeRequest: "logRequest"
          afterResponse: "logResponseDetails"
          capture:
            - regexp: '"token":\s*"([^"]+)"'
              as: "sessionToken"
            - regexp: '"cartId":\s*"([^"]+)"'
              as: "cartId"
          expect:
            - statusCode: 200
          think: 1

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions