You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Without fronting the GH.io deployment with some lambda/edge logic elsewhere (instead of just simple CNAME config for the domain with GitHub Pages proper), there won't be a way to support the curl -L https://testssl.sh installation — along with the HTML content on the same endpoint.
(It would be possible to migrate that logic to e.g. get.testssl.sh and dev.testssl.sh first, but question is who else may have that automagic output URL hardcoded and how much it would break any consumers…; also maintaining such hostnames still means taking care of server setup, certs etc.)
for curl -L https://testssl.sh: yeah, that can be replaced by e.g. using a subdomain like get. I know that could break things. For some reason there seem to be a more folks per day than I thought , like 700-800. It is strange though, as they are pulling the old 3.0.x version. They are not even polling it whether it changed, just downloads.
dev.testsst.sh is a playground for ciphers and headers only., unless you use http, then get redirected to github
Provide framework at github to automagically build a web site @ github with the DNS name testssl.sh.
Requirements:
Advantages:
The text was updated successfully, but these errors were encountered: