• In Docker Desktop, Windows 10 21H2, install Ddosify extension and try to connect to a server on localhost. The following result comes out with "connection refused" at the bottom for all requests.

⚙️ Initializing... 🔥 Engine fired.

✅ Successful Run: 0 0% ❌ Failed Run: 14 100% ⏱️ Avg. Duration: 0.00000s ✅ Successful Run: 0 0% ❌ Failed Run: 29 100% ⏱️ Avg. Duration: 0.00000s ✅ Successful Run: 0 0% ❌ Failed Run: 44 100% ⏱️ Avg. Duration: 0.00000s ✅ Successful Run: 0 0% ❌ Failed Run: 59 100% ⏱️ Avg. Duration: 0.00000s ✅ Successful Run: 0 0% ❌ Failed Run: 74 100% ⏱️ Avg. Duration: 0.00000s ✅ Successful Run: 0 0% ❌ Failed Run: 89 100% ⏱️ Avg. Duration: 0.00000s ✅ Successful Run: 0 0% ❌ Failed Run: 100 100% ⏱️ Avg. Duration: 0.00000s

RESULT

Success Count: 0 (0%) Failed Count: 100 (100%)

Durations (Avg):

Error Distribution (Count:Reason): 100 :connection refused

• I can connect to the "address:port" from browser without a problem.
• I tried different ports; no chance there neither.

Hi

Nice tool, I'm wondering if there is a way to send randomized data that follows a certain json definition? I see you have the config file, but i'm looking to send 1000s of request with generally unique bodies?

I've added these two packages to AUR:

https://aur.archlinux.org/packages/ddosify/ https://aur.archlinux.org/packages/ddosify-git/

I guess it's good to mention the installation of latest tag in README, please tell me if you prefer the git version (which installs the latest commit).

I have seen that we use some kind of formatted string for report output. I wonder if we can use json format (add a flag for configuring or sth.) for report output. I think structure will like below [ { // Step 1 "success_count":17, "failed_count":3, "duration":{ "dns":0.0007 // etc.. }, "status_code":{ "200":17 }, "error_distribution":{ "connection_timeout":3 } }, { // Step 2 things } ]

And also I think it's time to refactor using template as the code writted https://github.com/ddosify/ddosify/blob/master/core/report/stdout.go#L168

I recently installed Ddosify as an extension for Docker Desktop (windows) and tried it with localhost. I have a container up and running which can be accessed via port 80 and I can open it in the browser via http://localhost

When I do a load test, every single request fails:

Maybe I'm using it wrong, but I thought as a docker extension this is something I can use to test my local containers

Hi all,

First of all, thank you for this useful load testing tool. since its usage is decreasing the testing time in my project. On the other hand, I have a question related to the tool usage: ¿Is it possible to launch a load test in manual mode but with the incremental or waved type?. For now, I can specify a single load test with the three variants or a manual test with a different number of requests or duration. In this way, I would plot four different kinds of graphics: (1) Linear (2) Incremental (3) Waved (as is shown in the README.md) or (4) piecewise function (every stage of the function corresponds with a line in the manual_load JSON field). What I wanted to know is if I could create a request/seconds graphic with different forms. For example, the first step is a lineal load with X request during Y seconds and the second step is a waved load with J request in K seconds. I want something just like this: "manual_load": [ {"duration": Y, "count": X, "load_type": "linear"}, {"duration": K, "count": J, "load_type": "incremental"} ],

Thank you once again. Best regards, Daniel.

I can't find any options allowing ddosify to present a TLS client certificate to the server under test. Am I missing something or isn't that supported?

I understand that the problem here is between the keyboard and the chair, but it's not super user friendly. Better to strip https/http from the input or to give some message that it's not a valid domain.

here's my config

{ "request_count": 20, "load_type": "linear", "duration": 5, "manual_load": [ {"duration": 5, "count": 5}, {"duration": 6, "count": 10}, {"duration": 7, "count": 20} ], "steps": [ { "id": 1, "url": "https://localhost:56273/signin", "protocol": "https", "headers": { "Content-Type": "application/json", "Accept": "application/json" }, "method": "POST", "payload_multipart": [ { "name": "Username", "value": "admin" }, { "name": "Password", "value": "password" }, { "name": "Persist", "value": "false" }, { "name": "ReturnUrl", "value": "~/" } ], "timeout": 10 }, { "id": 2, "url": "https://.....................", "method": "GET", "timeout": 20, "sleep": "1000" } ] }

Problem

We were trying to benchmark a multi-tenant application locally, so were using localhost subdomains (e.g. test1.localhost & test2.localhost) to easily test multiple domains without any extra setup. Chrome & Firefox seem to resolve these to localhost as RFC-6761 section 6.3 says may be done. Other applications like curl don't treat this specially, but the host header can be overridden (e.g. curl localhost:8081 -H test.localhost:8081). I had hoped the same could be done in ddosify, but the host header seemed to get ignored.

For example, in one terminal I ran nc -l 8081, then in another I ran ddosify -t http://localhost:8081 -h 'Host: test.localhost:8081' -n 1 -d 1 which sent the following request to netcat

GET / HTTP/1.1
Host: localhost:8081
User-Agent: DdosifyHammer
Connection: close
Accept-Encoding: gzip

I was expecting

GET / HTTP/1.1
Host: test.localhost:8081
User-Agent: DdosifyHammer
Connection: close
Accept-Encoding: gzip

Solution

net/http.Request has a Host field that must be set in order to override the Host header, so I checked for the Host header key to set this field instead of adding the Host header to the http.Header map where it would get ignored.

Hello,

After run brew install ddosify/tap/ddosify I received this warning:

Warning: Calling bottle :unneeded is deprecated! There is no replacement.

Please report this issue to the ddosify/tap tap (not Homebrew/brew or Homebrew/core):
  /usr/local/Homebrew/Library/Taps/ddosify/homebrew-tap/Formula/ddosify.rb:10

On the 10th line of the ddosify.rb:

# typed: false
# frozen_string_literal: true

# This file was generated by GoReleaser. DO NOT EDIT.
class Ddosify < Formula
  desc "High-performance load testing tool, written in Golang."
  homepage "https://ddosify.com"
  version "0.4.1"
  license "AGPL-3.0-only"
  bottle :unneeded # <-- this line

  on_macos do
    if Hardware::CPU.intel?
    # ...

My system: macOS Mojave 10.14.6 Homebrew: 3.2.17

I tried a dynamic variable in URL as shown in the example in the documentation ddosify -t target_site.com/{{_randomInt}} and it works as expected.

But if I try the dynamic varilable in the domain like following ddosify -t https://{{_randomDomainWord}}.target_site.com i get following error: err: target is not valid: https://{{_randomDomainWord}}.target_site.com

I want to have a simple config.

Get a randomUUID from your function.

Do a POST call with that randomUUID called rid1 as a step 1

Do a GET call with same randomUUID, rid1 as a step 2.

This is currently not supported.

--

TLDR: Supporting variables throughout the config scope.

GraphQL operations that fail still return a 200 HTTP status code even if the inner resolvers fail How can ddosify be used with GraphQL operations?

I'd like to see ddosify fail when inner GraphQL resolvers fail. Right now there's a success for failed executions since the GraphQL response is 200 on the external response.

First of all, congratulations: I'm seriously considering making ddosify part of my daily stack. Here's what I see missing. When measuring latencies it is common practice to measure a certain percentile. It is also part of the SLA terminology, which this tool could help to assess. However, I didn't find a way to get a latency statistical distribution. Are you perhaps planning to add it? Cheers

Hi team!

I just arrived to your application, and it looks fairly simple to use and at the same time, really powerful, so congratulations on your side! 😃👍

I was wondering, have you thought of a way to "record" a user's navigation in the config.json format ? It would be really super useful for example, to really automate behaviours on a website.

Another option could also be to use other existing tools and try to "transform" the data format of each tool to ddosify's own format. For example, you could start from a .har or .js file provided by Chrome (the former if you export your navigation via network, the latter if you record a session) or else use tools like Postman with its .json format.

Best regards,