Unanswered question

After we migrate to AWS, we see "400 Bad Request" when checking user path

In our current environment (local data center and VM boxs), we successfully set a user path and run it in Neoload. However, after we migrated to AWS, when we tried setting up the same user path and checking it, we kept getting "400 Bad Request.The request could not be understood by the server due to malformed syntax. The client SHOULD NOT repeat the request without modifications." In our local environment, we did set up a variable extractor, but we could not find that variable in the user path we recorded on AWS. Can anyone help us? Thanks!

Tao Z.
Tao Z.

Tao Z.

Level
0
2 / 100
points

Answers

Nouredine A.
Nouredine A.

Nouredine A.

Level
4
5000 / 5000
points
Team

Have you tried a new recording against your AWS environment in order to compare with your local environment?