Handle 301 redirects in flow request ?

[avnerma]

I wonder if there is a way to automatically handle 301 response status code ?
we are created the following scenario -

scenarios:
    - flow:
      - get:
          url: "/api/last"
          capture:
            regexp: ".+"
            as: "id"            
          expect:
            - statusCode: 200     
      - get:
          url: "/api/{{ id }}/zip"
          capture:
            regexp: ".+"
            as: "url"    
          expect:
            - statusCode: 301  
      - get:
           url: "{{ url }}"
           expect:
             - statusCode: 200

and we getting error - "Failed expectations for request" on the last flow request.
Is there a better way to handle it ?

[hassy]

hi @avnerma 👋

is the last request (to the URL in url) supposed to be a redirect too?

if not, have you tried printing out the captured url to make sure it's a valid URL, i.e. with

- log: "url is: {{ url }}"

If it's the last step that's failing, it could be because the URL isn't captured properly