(LR) Support Tip: What to do when seeing 404 Not Found while replaying
Normally when replaying a during the enhancement stage of the same we face a lot of messages, normally this is fixed after adding correlation, however I have that many customers are creating the scripts and at the same time the application team is still releasing the software, so many time the 404 means there is something different while replaying than as it is set on the server actually, may be there are some paths that changed.
There are some recommendations in order to find the cause of the problem:
- Make sure all dynamic values have been correlated and correlation is correct.
- Compare Recording snapshot against replay snapshot in order to check what was sent while recording and what is actually seding the request on the replay.
- If you are sure about this part we will need to involve Fiddler, capture the BP until the part where you see the problem in the replay and compare the request sent in vugen while replay and how it is sent by the browser (captured in fiddler). This will show us the differences and if a new script recording is needed.
If you are customer you can try posting on our internal forums for more personalized support.
If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution