【问题标题】:Recorded scripts in jmeter gives 401 Unauthorized errorjmeter中记录的脚本给出401未经授权的错误
【发布时间】:2016-05-29 02:51:33
【问题描述】:

我正在尝试加载测试我的应用程序。但是当我尝试通过 jmeter 运行录制的脚本时,我只在几个特定页面上得到 401 Unauthorized 错误。该脚本在登录页面时运行,但在其他页面上出现错误。我需要使用多个用户(CSV 文件)运行整个场景 这是请求选项卡:

POST 数据: {"searchObject":{"LastName":"","FirstName":"","RoleId":"","StatusId":"","sortOrder":"Id","isAsc":"False", "isInactivated":false,"tempDataFlag":"True"},"isSorting":"false","listName":"CreissStaffList"}

Cookie Data:
ASP.NET_SessionId=0zqlv4t4ayszinlteqgnlrvg; __RequestVerificationToken=mmFzWMMfWojIH9J-32ylhW_8oseKWMP84XRZALQmUh0VfGmflM_kVW3b1MmWYLJ5ySCIezacyBFYplhzTSWMeo7CnMh2j14sD10qX2S_fq41

Request Headers:
Connection: keep-alive
Referer: https://www.creissmed.de/Admin/UserList
Accept-Language: en-US,en;q=0.5
X-Requested-With: XMLHttpRequest
Content-Type: application/json; charset=utf-8
Accept-Encoding: gzip, deflate
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:43.0) Gecko/20100101 Firefox/43.0
Accept: application/json, text/javascript, */*; q=0.01
Content-Length: 199

采样器结果:

Thread Name: Thread Group 1-1
Sample Start: 2016-02-17 17:17:05 IST
Load time: 142
Connect Time: 0
Latency: 142
Size in bytes: 1599
Headers size in bytes: 255
Body size in bytes: 1344
Sample Count: 1
Error Count: 1
Response code: 401
Response message: Unauthorized

Response headers:
HTTP/1.1 401 Unauthorized
Cache-Control: private
Content-Type: text/html
Location: /
Server: Microsoft-IIS/8.5
X-AspNetMvc-Version: 4.0
X-AspNet-Version: 4.0.30319
X-Powered-By: ASP.NET
Date: Wed, 17 Feb 2016 11:47:03 GMT
Content-Length: 1344


HTTPSampleResult fields:
ContentType: text/html
DataEncoding: iso-8859-1

这是 HTTP 请求页面的样子: 路径:/Admin/GetListData 身体参数:

{"searchObject":{"LastName":"","FirstName":"","RoleId":"","StatusId":"","sortOrder":"Id","isAsc":"False","isInactivated":false,"tempDataFlag":"True"},"isSorting":"false","listName":"CreissStaffList"}

我只在 GetListData HTTP 请求页面上遇到错误 提前致谢!

【问题讨论】:

    标签: jmeter performance-testing load-testing


    【解决方案1】:
    1. 添加View Results Tree 侦听器并检查响应详细信息。如果您没有看到错误消息,这并不一定意味着登录成功,尽管 HTTP 响应代码 200 页面可能包含错误。
    2. 您可能需要对__RequestVerificationToken 进行一些处理,因为这是反跨站点伪造实现,并且您需要进行一些关联才能绕过它。请参阅 How to Load Test CSRF-Protected Web Sites 指南以获取全面的说明和可能的选项。

    【讨论】:

      猜你喜欢
      • 1970-01-01
      • 1970-01-01
      • 1970-01-01
      • 1970-01-01
      • 1970-01-01
      • 1970-01-01
      • 2011-08-14
      • 1970-01-01
      • 2015-10-14
      相关资源
      最近更新 更多