requests sent via post are not causing any updates in the backend

[suvinad]

hi
i have the file that is attached and am running it with
ddosify -config D:\ToolsGroup\PerformanceTesting\DDosify\config.json

The output is as below

C:\Users\suvina_dsouza\go\bin>ddosify -config D:\ToolsGroup\PerformanceTesting\DDosify\config.json
⚙️  Initializing...
🔥 Engine fired.

🛑 CTRL+C to gracefully stop.
✔️  Successful Run: 0        0%       ❌ Failed Run: 0        0%       ⏱️  Avg. Duration: 0.00000s
✔️  Successful Run: 0        0%       ❌ Failed Run: 0        0%       ⏱️  Avg. Duration: 0.00000s
✔️  Successful Run: 0        0%       ❌ Failed Run: 0        0%       ⏱️  Avg. Duration: 0.00000s
✔️  Successful Run: 0        0%       ❌ Failed Run: 0        0%       ⏱️  Avg. Duration: 0.00000s
✔️  Successful Run: 0        0%       ❌ Failed Run: 0        0%       ⏱️  Avg. Duration: 0.00000s
✔️  Successful Run: 0        0%       ❌ Failed Run: 0        0%       ⏱️  Avg. Duration: 0.00000s
✔️  Successful Run: 0        0%       ❌ Failed Run: 0        0%       ⏱️  Avg. Duration: 0.00000s
✔️  Successful Run: 0        0%       ❌ Failed Run: 0        0%       ⏱️  Avg. Duration: 0.00000s
✔️  Successful Run: 0        0%       ❌ Failed Run: 0        0%       ⏱️  Avg. Duration: 0.00000s
✔️  Successful Run: 0        0%       ❌ Failed Run: 0        0%       ⏱️  Avg. Duration: 0.00000s
✔️  Successful Run: 1      100%       ❌ Failed Run: 0        0%       ⏱️  Avg. Duration: 19.59346s
✔️  Successful Run: 3      100%       ❌ Failed Run: 0        0%       ⏱️  Avg. Duration: 18.45059s


RESULT
-------------------------------------

1. load login form
---------------------------------
Success Count:    3     (100%)
Failed Count:     0     (0%)

Durations (Avg):
  DNS                  :0.0572s
  Connection           :0.0320s
  Request Write        :0.0000s
  Server Processing    :0.4901s
  Response Read        :0.0000s
  Total                :0.5793s

Status Code (Message) :Count
  200 (OK)    :3


2. post login form
---------------------------------
Success Count:    3     (100%)
Failed Count:     0     (0%)

Durations (Avg):
  DNS                  :0.0011s
  Connection           :0.0723s
  Request Write        :0.5819s
  Server Processing    :0.5005s
  Response Read        :0.7364s
  Total                :1.8922s

Status Code (Message) :Count
  200 (OK)    :3


3. select women category
---------------------------------
Success Count:    3     (100%)
Failed Count:     0     (0%)

Durations (Avg):
  DNS                  :0.0008s
  Connection           :0.0809s
  Request Write        :0.0000s
  Server Processing    :0.5798s
  Response Read        :0.0003s
  Total                :0.6618s

Status Code (Message) :Count
  200 (OK)    :3


4. select women category product
---------------------------------
Success Count:    3     (100%)
Failed Count:     0     (0%)

Durations (Avg):
  DNS                  :0.0008s
  Connection           :0.0809s
  Request Write        :0.0002s
  Server Processing    :0.4850s
  Response Read        :0.0000s
  Total                :0.5669s

Status Code (Message) :Count
  200 (OK)    :3


5. select add to cart
---------------------------------
Success Count:    3     (100%)
Failed Count:     0     (0%)

Durations (Avg):
  DNS                  :0.0008s
  Connection           :0.0800s
  Request Write        :0.2162s
  Server Processing    :0.5681s
  Response Read        :0.6543s
  Total                :1.5194s

Status Code (Message) :Count
  200 (OK)    :3


6. view cart
---------------------------------
Success Count:    3     (100%)
Failed Count:     0     (0%)

Durations (Avg):
  DNS                  :0.0008s
  Connection           :0.0803s
  Request Write        :0.4314s
  Server Processing    :0.5698s
  Response Read        :0.6362s
  Total                :1.7185s

Status Code (Message) :Count
  200 (OK)    :3


7. proceed to checkout
---------------------------------
Success Count:    3     (100%)
Failed Count:     0     (0%)

Durations (Avg):
  DNS                  :0.0009s
  Connection           :0.0782s
  Request Write        :0.4322s
  Server Processing    :0.5706s
  Response Read        :0.6488s
  Total                :1.7308s

Status Code (Message) :Count
  200 (OK)    :3


8. proceed to pay
---------------------------------
Success Count:    3     (100%)
Failed Count:     0     (0%)

Durations (Avg):
  DNS                  :0.0007s
  Connection           :0.0809s
  Request Write        :0.0002s
  Server Processing    :0.5595s
  Response Read        :0.0000s
  Total                :0.6414s

Status Code (Message) :Count
  200 (OK)    :3


9. revisit cart
---------------------------------
Success Count:    3     (100%)
Failed Count:     0     (0%)

Durations (Avg):
  DNS                  :0.0054s
  Connection           :0.0775s
  Request Write        :0.4389s
  Server Processing    :0.5606s
  Response Read        :0.6654s
  Total                :1.7478s

Status Code (Message) :Count
  200 (OK)    :3


10. remove item cart
---------------------------------
Success Count:    3     (100%)
Failed Count:     0     (0%)

Durations (Avg):
  DNS                  :0.0458s
  Connection           :0.0765s
  Request Write        :0.4416s
  Server Processing    :0.5701s
  Response Read        :0.6746s
  Total                :1.8086s

Status Code (Message) :Count
  200 (OK)    :3


11. view profile
---------------------------------
Success Count:    3     (100%)
Failed Count:     0     (0%)

Durations (Avg):
  DNS                  :0.0202s
  Connection           :0.0768s
  Request Write        :0.2336s
  Server Processing    :0.5636s
  Response Read        :0.7698s
  Total                :1.6640s

Status Code (Message) :Count
  200 (OK)    :3


12. edit profile
---------------------------------
Success Count:    3     (100%)
Failed Count:     0     (0%)

Durations (Avg):
  DNS                  :0.0217s
  Connection           :0.0789s
  Request Write        :0.2191s
  Server Processing    :0.5646s
  Response Read        :0.7360s
  Total                :1.6203s

Status Code (Message) :Count
  200 (OK)    :3


13. update profile
---------------------------------
Success Count:    3     (100%)
Failed Count:     0     (0%)

Durations (Avg):
  DNS                  :0.0009s
  Connection           :0.0934s
  Request Write        :0.0000s
  Server Processing    :0.6144s
  Response Read        :0.0000s
  Total                :0.7087s

Status Code (Message) :Count
  400 (Bad Request)    :3


14. logout
---------------------------------
Success Count:    3     (100%)
Failed Count:     0     (0%)

Durations (Avg):
  DNS                  :0.0027s
  Connection           :0.0778s
  Request Write        :0.2143s
  Server Processing    :0.5617s
  Response Read        :0.7346s
  Total                :1.5909s

Status Code (Message) :Count
  200 (OK)    :3

---

• In the initial start of the run, i see 0%, why is that?
• Although all my requests are ok, i dont see any updates happening in the backend; for example: an item actually getting added to the cart, is there any issue in my code?
• How can i be sure that my post requests have succeeded, if there are not updates visible in my application?
• At step 13. update profile, the output is bad request(400) , but the step shows as succeeded, why is that?

config.json.txt

[kursataktas]

Hi @suvinad

In the initial start of the run, i see 0%, why is that?

Ddosify prints the current situation every 1.5 seconds. Since your scenario has 14 steps, it takes longer to complete a run.

Although all my requests are ok, i dont see any updates happening in the backend; for example: an item actually getting added to the cart, is there any issue in my code?

As far as I can see all steps received HTTP response with status codes. So your server has received the requests and sent the response. But the configuration files contain errors;

1. The first step contains sample headers values that we provide on our example config file. Also, you've enabled the HTTP2 via h2: true field.
2. Steps that uses POST method sends data with payload_mutlipart. payload_mutlipart is for multipart/form-data request and it automatically adds Content-Type: multipart/form-data; header. So if your endpoint does not accept this payload type, then you should use the proper one. I think payload_file would be OK for your endpoint. You can pass a JSON file directly.
3. If any request requires authentication, you need to arrange the config file according to the authentication type. Ddosify supports basic auth and token based auths.

At step 13. update profile, the output is bad request(400) , but the step shows as succeeded, why is that?

If Ddosify receives the response from the endpoint, then it marks that request as Successful no matter the status code.

After that fixes if you need more help, don't hesitate to contact us on Discord. We can help you faster in there.

[suvinad]

Thank you for the reply:
messaged you at https://discord.com/channels/898523141788287017/899302721411223582/951837413108498473

i have modified the config.json to use payload_file; i have also removed unneeded headers, however i get bad request at steps 2 and 13
please see attached files
config.json.txt
postloginform.json.txt
postupdateprofileform.json.txt

C:\Users\suvina_dsouza\go\bin>ddosify -config D:\ToolsGroup\PerformanceTesting\DDosify\config.json
⚙️  Initializing...
🔥 Engine fired.

🛑 CTRL+C to gracefully stop.
✔️  Successful Run: 0        0%       ❌ Failed Run: 0        0%       ⏱️  Avg. Duration: 0.00000s
✔️  Successful Run: 0        0%       ❌ Failed Run: 0        0%       ⏱️  Avg. Duration: 0.00000s
✔️  Successful Run: 0        0%       ❌ Failed Run: 0        0%       ⏱️  Avg. Duration: 0.00000s
✔️  Successful Run: 0        0%       ❌ Failed Run: 0        0%       ⏱️  Avg. Duration: 0.00000s
✔️  Successful Run: 0        0%       ❌ Failed Run: 0        0%       ⏱️  Avg. Duration: 0.00000s
✔️  Successful Run: 0        0%       ❌ Failed Run: 0        0%       ⏱️  Avg. Duration: 0.00000s
✔️  Successful Run: 0        0%       ❌ Failed Run: 0        0%       ⏱️  Avg. Duration: 0.00000s
✔️  Successful Run: 0        0%       ❌ Failed Run: 0        0%       ⏱️  Avg. Duration: 0.00000s
✔️  Successful Run: 0        0%       ❌ Failed Run: 0        0%       ⏱️  Avg. Duration: 0.00000s
✔️  Successful Run: 0        0%       ❌ Failed Run: 0        0%       ⏱️  Avg. Duration: 0.00000s
✔️  Successful Run: 0        0%       ❌ Failed Run: 0        0%       ⏱️  Avg. Duration: 0.00000s
✔️  Successful Run: 1      100%       ❌ Failed Run: 0        0%       ⏱️  Avg. Duration: 22.02358s
✔️  Successful Run: 2      100%       ❌ Failed Run: 0        0%       ⏱️  Avg. Duration: 22.57152s
✔️  Successful Run: 3      100%       ❌ Failed Run: 0        0%       ⏱️  Avg. Duration: 22.96959s


RESULT
-------------------------------------

1. load login form
---------------------------------
Success Count:    3     (100%)
Failed Count:     0     (0%)

Durations (Avg):
  DNS                  :0.0369s
  Connection           :0.1150s
  Request Write        :0.0000s
  Server Processing    :0.4618s
  Response Read        :0.0000s
  Total                :0.6137s

Status Code (Message) :Count
  200 (OK)    :3


2. post login form
---------------------------------
Success Count:    3     (100%)
Failed Count:     0     (0%)

Durations (Avg):
  DNS                  :0.0032s
  Connection           :0.1194s
  Request Write        :0.0002s
  Server Processing    :0.5153s
  Response Read        :0.0003s
  Total                :0.6384s

Status Code (Message) :Count
  400 (Bad Request)    :3


3. select women category
---------------------------------
Success Count:    3     (100%)
Failed Count:     0     (0%)

Durations (Avg):
  DNS                  :0.0010s
  Connection           :0.1189s
  Request Write        :0.0002s
  Server Processing    :0.5579s
  Response Read        :0.0000s
  Total                :0.6780s

Status Code (Message) :Count
  200 (OK)    :3


4. select women category product
---------------------------------
Success Count:    3     (100%)
Failed Count:     0     (0%)

Durations (Avg):
  DNS                  :0.0007s
  Connection           :0.1239s
  Request Write        :0.0000s
  Server Processing    :0.5384s
  Response Read        :0.0000s
  Total                :0.6631s

Status Code (Message) :Count
  200 (OK)    :3


5. select add to cart
---------------------------------
Success Count:    3     (100%)
Failed Count:     0     (0%)

Durations (Avg):
  DNS                  :0.0010s
  Connection           :0.1206s
  Request Write        :0.4886s
  Server Processing    :0.6078s
  Response Read        :0.7314s
  Total                :1.9493s

Status Code (Message) :Count
  200 (OK)    :3


6. view cart
---------------------------------
Success Count:    3     (100%)
Failed Count:     0     (0%)

Durations (Avg):
  DNS                  :0.0006s
  Connection           :0.1232s
  Request Write        :0.4826s
  Server Processing    :0.6089s
  Response Read        :0.7353s
  Total                :1.9507s

Status Code (Message) :Count
  200 (OK)    :3


7. proceed to checkout
---------------------------------
Success Count:    3     (100%)
Failed Count:     0     (0%)

Durations (Avg):
  DNS                  :0.0010s
  Connection           :0.1219s
  Request Write        :0.7306s
  Server Processing    :0.6063s
  Response Read        :0.7354s
  Total                :2.1951s

Status Code (Message) :Count
  200 (OK)    :3


8. proceed to pay
---------------------------------
Success Count:    3     (100%)
Failed Count:     0     (0%)

Durations (Avg):
  DNS                  :0.0012s
  Connection           :0.1194s
  Request Write        :0.0002s
  Server Processing    :0.6175s
  Response Read        :0.0000s
  Total                :0.7382s

Status Code (Message) :Count
  200 (OK)    :3


9. revisit cart
---------------------------------
Success Count:    3     (100%)
Failed Count:     0     (0%)

Durations (Avg):
  DNS                  :0.0223s
  Connection           :0.1211s
  Request Write        :0.7506s
  Server Processing    :0.6021s
  Response Read        :0.7683s
  Total                :2.2645s

Status Code (Message) :Count
  200 (OK)    :3


10. remove item cart
---------------------------------
Success Count:    3     (100%)
Failed Count:     0     (0%)

Durations (Avg):
  DNS                  :0.0144s
  Connection           :0.1203s
  Request Write        :0.7550s
  Server Processing    :0.6189s
  Response Read        :0.7558s
  Total                :2.2644s

Status Code (Message) :Count
  200 (OK)    :3


11. view profile
---------------------------------
Success Count:    3     (100%)
Failed Count:     0     (0%)

Durations (Avg):
  DNS                  :0.0171s
  Connection           :0.1177s
  Request Write        :0.5097s
  Server Processing    :0.6160s
  Response Read        :0.8932s
  Total                :2.1538s

Status Code (Message) :Count
  200 (OK)    :3


12. edit profile
---------------------------------
Success Count:    3     (100%)
Failed Count:     0     (0%)

Durations (Avg):
  DNS                  :0.0009s
  Connection           :0.1235s
  Request Write        :0.2441s
  Server Processing    :0.6142s
  Response Read        :0.8561s
  Total                :1.8388s

Status Code (Message) :Count
  200 (OK)    :3


13. update profile
---------------------------------
Success Count:    3     (100%)
Failed Count:     0     (0%)

Durations (Avg):
  DNS                  :0.0048s
  Connection           :0.1193s
  Request Write        :0.0002s
  Server Processing    :0.7270s
  Response Read        :0.0003s
  Total                :0.8516s

Status Code (Message) :Count
  400 (Bad Request)    :3


14. reload updated profile
---------------------------------
Success Count:    3     (100%)
Failed Count:     0     (0%)

Durations (Avg):
  DNS                  :0.0008s
  Connection           :0.1223s
  Request Write        :0.4906s
  Server Processing    :0.6106s
  Response Read        :0.8672s
  Total                :2.0915s

Status Code (Message) :Count
  200 (OK)    :3


15. logout
---------------------------------
Success Count:    3     (100%)
Failed Count:     0     (0%)

Durations (Avg):
  DNS                  :0.0011s
  Connection           :0.1297s
  Request Write        :0.4842s
  Server Processing    :0.6082s
  Response Read        :0.8553s
  Total                :2.0785s

Status Code (Message) :Count
  200 (OK)    :3


C:\Users\suvina_dsouza\go\bin>

The requests and payload as viewed at developer tools are here:
Step2:

Request URL: http://webapp-attack.azurewebsites.net/login
Request Method: POST
Status Code: 302 FOUND
Remote Address: 20.40.202.25:80
Referrer Policy: strict-origin-when-cross-origin
Content-Length: 208
Content-Type: text/html; charset=utf-8
Date: Fri, 11 Mar 2022 13:35:02 GMT
Location: http://webapp-attack.azurewebsites.net/
Server: gunicorn
Set-Cookie: session=eyJlbWFpbCI6InN1dmluYWRAZ21haWwuY29tIn0.YitQBg.QJPeuPIoqP_kD43rXdjKC7B8Kf4; HttpOnly; Path=/
Vary: Cookie
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,image/apng,*/*;q=0.8,application/signed-exchange;v=b3;q=0.9
Accept-Encoding: gzip, deflate
Accept-Language: en-US,en;q=0.9
Cache-Control: max-age=0
Connection: keep-alive
Content-Length: 43
Content-Type: application/x-www-form-urlencoded
Host: webapp-attack.azurewebsites.net
Origin: http://webapp-attack.azurewebsites.net
Referer: http://webapp-attack.azurewebsites.net/loginForm
Upgrade-Insecure-Requests: 1
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/99.0.4844.51 Safari/537.36

payload of step2:

email: suvinad@gmail.com
password: start123

source:email=suvinad%40gmail.com&password=start123

step13

Request URL: http://webapp-attack.azurewebsites.net/updateProfile
Request Method: POST
Status Code: 302 FOUND
Remote Address: 20.40.202.25:80
Referrer Policy: strict-origin-when-cross-origin
Content-Length: 248
Content-Type: text/html; charset=utf-8
Date: Fri, 11 Mar 2022 13:39:53 GMT
Location: http://webapp-attack.azurewebsites.net/account/profile/edit
Server: gunicorn
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,image/apng,*/*;q=0.8,application/signed-exchange;v=b3;q=0.9
Accept-Encoding: gzip, deflate
Accept-Language: en-US,en;q=0.9
Cache-Control: max-age=0
Connection: keep-alive
Content-Length: 133
Content-Type: application/x-www-form-urlencoded
Cookie: session=eyJlbWFpbCI6InN1dmluYWRAZ21haWwuY29tIn0.YitQBg.QJPeuPIoqP_kD43rXdjKC7B8Kf4
Host: webapp-attack.azurewebsites.net
Origin: http://webapp-attack.azurewebsites.net
Referer: http://webapp-attack.azurewebsites.net/account/profile/edit
Upgrade-Insecure-Requests: 1
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/99.0.4844.51 Safari/537.36

payload for step13

email: suvinad@gmail.com
firstName: suvina
lastName: dsouza
address1: goa
address2: 
zipcode: 
city: merces
state: goa
country: india
phone: 

source:
email=suvinad%40gmail.com&firstName=suvina&lastName=dsouza&address1=goa&address2=&zipcode=&city=merces&state=goa&country=india&phone=

[suvinad]

hi @kursataktas

thank you for giving me a hint on the type of body the server expects, i replaced it with
and everything worked like a breeze !!! :-)

this is what i did for it to work:
"Content-Type": "application/x-www-form-urlencoded"

C:\Users\suvina_dsouza\go\bin>ddosify -config D:\ToolsGroup\PerformanceTesting\DDosify\config.json
⚙️  Initializing...
🔥 Engine fired.

🛑 CTRL+C to gracefully stop.
✔️  Successful Run: 0        0%       ❌ Failed Run: 0        0%       ⏱️  Avg. Duration: 0.00000s
✔️  Successful Run: 0        0%       ❌ Failed Run: 0        0%       ⏱️  Avg. Duration: 0.00000s
✔️  Successful Run: 0        0%       ❌ Failed Run: 0        0%       ⏱️  Avg. Duration: 0.00000s
✔️  Successful Run: 0        0%       ❌ Failed Run: 0        0%       ⏱️  Avg. Duration: 0.00000s
✔️  Successful Run: 0        0%       ❌ Failed Run: 0        0%       ⏱️  Avg. Duration: 0.00000s
✔️  Successful Run: 0        0%       ❌ Failed Run: 0        0%       ⏱️  Avg. Duration: 0.00000s
✔️  Successful Run: 0        0%       ❌ Failed Run: 0        0%       ⏱️  Avg. Duration: 0.00000s
✔️  Successful Run: 0        0%       ❌ Failed Run: 0        0%       ⏱️  Avg. Duration: 0.00000s
✔️  Successful Run: 0        0%       ❌ Failed Run: 0        0%       ⏱️  Avg. Duration: 0.00000s
✔️  Successful Run: 0        0%       ❌ Failed Run: 0        0%       ⏱️  Avg. Duration: 0.00000s
✔️  Successful Run: 0        0%       ❌ Failed Run: 0        0%       ⏱️  Avg. Duration: 0.00000s
✔️  Successful Run: 0        0%       ❌ Failed Run: 0        0%       ⏱️  Avg. Duration: 0.00000s
✔️  Successful Run: 0        0%       ❌ Failed Run: 0        0%       ⏱️  Avg. Duration: 0.00000s
✔️  Successful Run: 1      100%       ❌ Failed Run: 0        0%       ⏱️  Avg. Duration: 29.77758s
✔️  Successful Run: 1      100%       ❌ Failed Run: 0        0%       ⏱️  Avg. Duration: 29.77758s
✔️  Successful Run: 3      100%       ❌ Failed Run: 0        0%       ⏱️  Avg. Duration: 28.37546s


RESULT
-------------------------------------

1. load login form
---------------------------------
Success Count:    3     (100%)
Failed Count:     0     (0%)

Durations (Avg):
  DNS                  :0.0340s
  Connection           :0.0538s
  Request Write        :0.0004s
  Server Processing    :0.4884s
  Response Read        :0.0000s
  Total                :0.5765s

Status Code (Message) :Count
  200 (OK)    :3


2. post login form
---------------------------------
Success Count:    3     (100%)
Failed Count:     0     (0%)

Durations (Avg):
  DNS                  :0.0010s
  Connection           :0.0566s
  Request Write        :0.4678s
  Server Processing    :0.5378s
  Response Read        :0.6168s
  Total                :1.6800s

Status Code (Message) :Count
  200 (OK)    :3


3. select women category
---------------------------------
Success Count:    3     (100%)
Failed Count:     0     (0%)

Durations (Avg):
  DNS                  :0.0010s
  Connection           :0.0606s
  Request Write        :0.0000s
  Server Processing    :0.5695s
  Response Read        :0.0000s
  Total                :0.6311s

Status Code (Message) :Count
  200 (OK)    :3


4. select women category product
---------------------------------
Success Count:    3     (100%)
Failed Count:     0     (0%)

Durations (Avg):
  DNS                  :0.0009s
  Connection           :0.0607s
  Request Write        :0.0000s
  Server Processing    :0.5659s
  Response Read        :0.0000s
  Total                :0.6276s

Status Code (Message) :Count
  200 (OK)    :3


5. select add to cart
---------------------------------
Success Count:    3     (100%)
Failed Count:     0     (0%)

Durations (Avg):
  DNS                  :0.0010s
  Connection           :0.0585s
  Request Write        :0.6217s
  Server Processing    :0.5634s
  Response Read        :0.6201s
  Total                :1.8647s

Status Code (Message) :Count
  200 (OK)    :3


6. view cart
---------------------------------
Success Count:    3     (100%)
Failed Count:     0     (0%)

Durations (Avg):
  DNS                  :0.0011s
  Connection           :0.0570s
  Request Write        :0.6290s
  Server Processing    :0.5651s
  Response Read        :0.6254s
  Total                :1.8777s

Status Code (Message) :Count
  200 (OK)    :3


7. proceed to checkout
---------------------------------
Success Count:    3     (100%)
Failed Count:     0     (0%)

Durations (Avg):
  DNS                  :0.0009s
  Connection           :0.0588s
  Request Write        :0.6230s
  Server Processing    :0.5637s
  Response Read        :0.6194s
  Total                :1.8658s

Status Code (Message) :Count
  200 (OK)    :3


8. proceed to pay
---------------------------------
Success Count:    3     (100%)
Failed Count:     0     (0%)

Durations (Avg):
  DNS                  :0.0007s
  Connection           :0.0618s
  Request Write        :0.0000s
  Server Processing    :0.5560s
  Response Read        :0.0003s
  Total                :0.6188s

Status Code (Message) :Count
  200 (OK)    :3


9. revisit cart
---------------------------------
Success Count:    3     (100%)
Failed Count:     0     (0%)

Durations (Avg):
  DNS                  :0.0061s
  Connection           :0.0593s
  Request Write        :1.7255s
  Server Processing    :0.5537s
  Response Read        :1.7409s
  Total                :4.0856s

Status Code (Message) :Count
  200 (OK)    :3


10. remove item cart
---------------------------------
Success Count:    3     (100%)
Failed Count:     0     (0%)

Durations (Avg):
  DNS                  :1.2209s
  Connection           :0.0536s
  Request Write        :0.4112s
  Server Processing    :0.5570s
  Response Read        :0.6232s
  Total                :2.8659s

Status Code (Message) :Count
  200 (OK)    :3


11. view profile
---------------------------------
Success Count:    3     (100%)
Failed Count:     0     (0%)

Durations (Avg):
  DNS                  :0.0257s
  Connection           :0.0578s
  Request Write        :1.7028s
  Server Processing    :0.5544s
  Response Read        :1.7706s
  Total                :4.1112s

Status Code (Message) :Count
  200 (OK)    :3


12. edit profile
---------------------------------
Success Count:    3     (100%)
Failed Count:     0     (0%)

Durations (Avg):
  DNS                  :0.0011s
  Connection           :0.0632s
  Request Write        :0.0004s
  Server Processing    :0.5556s
  Response Read        :0.6833s
  Total                :1.3036s

Status Code (Message) :Count
  200 (OK)    :3


13. update profile
---------------------------------
Success Count:    3     (100%)
Failed Count:     0     (0%)

Durations (Avg):
  DNS                  :0.0010s
  Connection           :0.0637s
  Request Write        :0.2269s
  Server Processing    :0.6137s
  Response Read        :1.6531s
  Total                :2.5583s

Status Code (Message) :Count
  200 (OK)    :3


14. reload updated profile
---------------------------------
Success Count:    3     (100%)
Failed Count:     0     (0%)

Durations (Avg):
  DNS                  :0.0010s
  Connection           :0.0633s
  Request Write        :0.4134s
  Server Processing    :0.5599s
  Response Read        :0.6932s
  Total                :1.7307s

Status Code (Message) :Count
  200 (OK)    :3


15. logout
---------------------------------
Success Count:    3     (100%)
Failed Count:     0     (0%)

Durations (Avg):
  DNS                  :0.0011s
  Connection           :0.0630s
  Request Write        :0.5411s
  Server Processing    :0.5735s
  Response Read        :0.7992s
  Total                :1.9778s

Status Code (Message) :Count
  200 (OK)    :3


C:\Users\suvina_dsouza\go\bin>

[suvinad]

hi @kursataktas

i had a couple of questions based on my load run(attached output) and based on the scenario in the config file ( attached)

1. I have a request count of 300 and duration of 60 secs for the scenario in the config file

• does this mean the entire scenario executes in 60secs, ie all 300 requests get covered up in 60s

2. all successful runs show 0%, however i do see some successes in the output

• can you tell me how to interpret the report in terms of each of its fields

3. how is linear load different from incremental load different from waved load: can this be understood from the request count
   as to the naked eye everything seems linear

4. does the tool simulate parallel load, like all 300 requests coming in at the same time

5. does the tool support parametrization, like reading data from a csv file or excel sheet or database table and submitting these
   to the request payload

6. Any logical conditions/assertions supported?

7. what is the difference between jmeter / ddosify in terms of capability? can i get some reasons why ddosify can be a good fit over UI tools like Jmeter; in what scenarios?

8. Can ddosify show how a request gets broken down internally ( example if there are any db connection requests, any other urls getting loaded in between etc)

9. Can the tool show where are the performance bottlenecks ( example: cpu, memory,network bandwidth etc)

10.Is there a way to get the content of the response in terms of response headers,response data for every request

output_Run_Config.json.txt
config.json.txt

[kursataktas]

Hi @suvinad

1. Yes, that's true.
2. Ddosify marks the iteration/run as successful if and only if all the steps are successful. For example, let's say you have a scenario that includes 2 steps. If the result of these two steps is successful then we can say that iteration is successful. If any of the steps failed that means the whole iteration is failed. By the way iteration count(run count) represents the execution count of the Scenario(steps). You are supplying it as request_count in the config file. But we will change its' name to iteration_count.
3. As shown in the readme, load type determines the concurrent iteration per second across time.
4. Yes. For example, let's say request_count is 100 and duration is 10. Ddosify sends 10 concurrent requests per second for 10 seconds.
5. Not yet. It is in our road map and it will be available soon.
6. Just like the parameterization, this will be available soon. The parameterization/correlation concept will be like Postman.
7. The main difference is about performance. Ddosify is able to send more concurrent requests than JMeter. On the other hand, JMeter has GUI and more network protocol support. There are other pros and cons between them but it really depends on your use case to choose the right tool. If the UI is the only concerning thing, you can take a look at Ddosify Cloud when it is ready. Here is the Live Demo to see what it looks like.
8. I didn't understand the question. Would you be more specific?
9. No. I don't know any other load testing tool that does that too. I think this is out of the scope for load testing tools. You can achieve this by APM tools like Datadog / New Relic, etc. For example, start the load test and investigate the APM dashboards to find the bottlenecks.
10. No. Just like the previous question, I think this requirement is in the scope of APM or logging solution.

[suvinad]

Thanks @kursataktas for the reply

by point 8 i meant:

1. does the tool have a provision to show breakdown of each request and time taken
   example: registration on a website
   a.load registration page
   b.submit registration data ( here we will have a database connection between application server and web server update- would this time get captured, can this be shown)
   c.get response if registration succeeded

[kursataktas]

Output shows the aggregated results of each step.
For example, below one shows the logout step details.

 15. logout
---------------------------------
Success Count:    3     (100%)
Failed Count:     0     (0%)

Durations (Avg):
  DNS                  :0.0011s
  Connection           :0.0630s
  Request Write        :0.5411s
  Server Processing    :0.5735s
  Response Read        :0.7992s
  Total                :1.9778s

Status Code (Message) :Count
  200 (OK)    :3

Ddosify sends requests to the endpoints you provide. Then collects the metrics from the response and shows the aggregated report. Ddosify can't know what is happening between your application server and database.

                                                   -------- Your Server ------
                ---- request ----->                |                         |
DDOSIFY                                            | App  --- request -->  DB|
                <--- response ----                 |                         |
                                                   ---------------------------

Collecting metrics from your server is the responsibility of the APM tools.

[suvinad]

Thank you @kursataktas
I think JMeter does this out of the box