We will try to reproduce that issue. Meanwhile as workaround you can change the type of the next request from "Follow the redirect..." to "Manual definition" and extract the new path from the previous server response.
I had already change the type of the request to "manual definition".
I asked devs why the url contains a '//'.
As it's works on 5.1 I hope you will reproduce that issue and understand why it is not working on 5.4
We were able to reproduce that issue but like you said the // in the middle of the URL is probably a mistake from the developers of the application. It is expected at the beginning but not in the middle.
5.1 and 5.4 are using different HTTP client that's why the behavior is different. Anyway, we will handle such use case in next NeoLoad versions.
No similar question