grouping requests after redirect

[mblakele]

#228 asked a similar question, but I don't think it handles the use case where a request redirects.

self.get('/fubar/') # redirects to /fubar/1234/abcd

I don't know what the redirect will look like in advance, so I can't skip it. But I'd like to group all those requests under one path, because the trailing segments are different for every locust. Adding name=/fubar/ to the initial request didn't seem to do this. Is there another way?

Operationally, I think it would make sense to configure the client in on_start so that all requests matching some pattern will be reported as /fubar/baz.

[cyberw]

Closing this due to lack of activity. Let me know if you want to reopen.

[heyman]

If you let requests follow the redirect automatically (the default behaviour) all the actual requests will be grouped under a single stats entry (and the response time will be for the whole redirect chain) named after either the first URL, or the name parameter if it was specified.