ExpectedResponseUrl 错误是 Visual Studio 2010 Web 性能测试
我在 Visual Studio 2010 中为一个 Web 应用程序录制了一个 Web 性能测试，该应用程序使用 Windows Live ID 和安全令牌服务来进行用户身份验证。
我的录音中有两个请求发送到 https://login.live.com/ 并且它们工作正常在我记录测试后，在 Visual Studio Test Runner 上，但大约一天后，我开始收到一条错误消息，指出上述请求的“ExpectedResponseUrl 属性的值不等于实际响应 URL”。我知道我可以关闭响应 URL 验证规则，但这并不能解决问题的根本原因，只能掩盖症状。
我想知道是否有人知道这里发生了什么事？我的猜测是浏览器级别有缓存数据，但我无法以某种方式证明这一点。
I have recorded a Web Performance Test in Visual Studio 2010 for a web application that uses Windows Live ID with Secure Token Service for the authentication of the user.
There are two requests in my recording that go to https://login.live.com/ and they work fine on the Visual Studio Test Runner after I recorded the test, but then after about a day later I start to get an error message that states "The value of the ExpectedResponseUrl property does not equal the actual response URL" on the requests mentioned. I understand that I can turn off the Response URL validation rules, but that doesn't fix the root cause of the problem and only masks the symptoms.
I was wondering if anyone knows what is going on here? My guess is that there is cached data at the browser level, but I haven't been able to prove that one way or another.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
您可能在一段时间后“过期”的回发字段中记录了一个值。我愿意你从请求中返回的 url 现在是一个错误页面。
如果您熟悉 C#，我发现将测试更改为编码测试并仔细查看发送到 login.live.com 的所有字段会更容易。
您可能需要大量有关 login.live.com 工作原理的信息才能真正了解其真相。
Chances are you recorded a value in one of the post back fields that "expires" after a period of time. I am willing to be the url you are getting back from the request is now an error page.
If you are familiar with C#, I find it is easier to change the test to a coded test and have a really close look at all the fields that are being sent to login.live.com.
You would probably need a fair bit of information on how login.live.com works to really get to the bottom of it.