After manually editing the .orequest.body and .stump files for existing stumps on a local machine, then restarting the service and verifying they are served properly, it appears that the OriginalRequest's EndPoint properties in the .stump file were wiped out and set to 0.0.0.0:0.
I edited the requests of a number of existing stumps locally, updating the orequest.body and .stump files, then restarting the service. My changes were limited to:
changing the .server DisableStumpsWhenRecording to true
changing a card number sequence in the request xml of the orequest.body
changing the two BodyMatchRule properties in the .stump file. The stump name was also changed, but this was done through the website ui.
After saving these changes and restarting the stumps service, I verified that my altered stumps were being served properly, and changed the DisableStumpsWhenRecording back to false.
At this point I reviewed the .stump files that I had changed, and the LocalEndPoint and RemoteEndPoint properties of the OriginalRequest appeared to have been changed to 0.0.0.0:0.
After manually editing the .orequest.body and .stump files for existing stumps on a local machine, then restarting the service and verifying they are served properly, it appears that the OriginalRequest's EndPoint properties in the .stump file were wiped out and set to 0.0.0.0:0.
I edited the requests of a number of existing stumps locally, updating the orequest.body and .stump files, then restarting the service. My changes were limited to:
At this point I reviewed the .stump files that I had changed, and the LocalEndPoint and RemoteEndPoint properties of the OriginalRequest appeared to have been changed to 0.0.0.0:0.