issues dealing with self signed certificates?

[hmacias-avaya]

I tried running some HTTPS requests against my server (just a simple GET request) but I do not see any request arriving.
Other than the "0" before the "0ms" on the output, I don't see anything indicating an issue.

I then tried pointing it to some non-existing server:

goku -t https://does_not_exist/ -v

the output doesn't seem to indicate any issue. Using -v provided very little extra information

[Client 0 Iteration 0] 0 0ms



Concurrency level 1
Time taken 0 seconds
Total requests  1
Mean request time 0 ms
Max request time 0 ms
Min request time 0 ms
95'th percentile: 0 ms
99.9'th percentile: 0 ms

If I switch to HTTP to my server, I do see requests arriving and instead of the "0" I do see the requests and some status code in goku's output.
Is it possible that since my server's certificate is not trusted (it's self signed) goku is not even sending the request? is there any way to confirm or try telling goku to still connect ignoring certificate checks?

[jcaromiq]

Hello, thank you for using it and reporting the issue.
With the details you have provided, I have been able to reproduce it, so I need to apply a fix to handle self-signed certificates and also to provide more feedback on the status code. I will keep you informed.

[jcaromiq]

Hi @hmacias-avaya
It's already solved at 1.1.6, sorry for the inconvenience.
thank you

[hmacias-avaya]

no need to be sorry! thank you for the quick fix, it's working fine.