Show HN: My shell script for HTTP/HTTPS troubleshooting and profiling

[wink]

Not to rain on your parade with nicely formatted code like hardly any shell projects do, but what I would have expected for such a tool that I just want to use:

wget https://github/.../releases/.../stable/htrace.sh

Only gave it a quick look and saw the other comment asking for dependencies. if there are some, why not list them in the README.

I'm really not against installers, but falls under the "small handy tool" category and not "I will spend time automating the install, either it works or it doesn't"

[kylek]

You're crazy. This fellow deserves all of today's internet points. He even has a man page!

[bloopernova]

This page talks about which packages to install, and how to install them:

https://github.com/trimstray/htrace.sh/issues/18

Those instructions definitely need to be in the installation section!!

[newman314]

For that, look to testssl.sh (https://github.com/drwetter/testssl.sh)

[salamander014]

Plug for a related tool that I use constantly.

It's called Swiss Army Knife for SMTP, or "SWAKS" for short.

http://www.jetmore.org/john/code/swaks/

This tool is one of the best tools I've ever seen. It's well thought out, well designed, and the documentation is very usable.

(Full disclosure: I have no affiliation with the author or the tool.)

[bloopernova]

One comment: put the list of package dependencies before the install, or check for their packages during setup.sh

Make life a little easier for the user ;)

[natch]

Looks really cool.

Why are you using a URL in place of a domain name, in the invocation example? Seems confusing. I would expect to see just a domain name there. Although I wouldn't complain if it works with both a domain and a full URL, automatically stripping off the parts it doesn't need. Also seeing http:// instead of https:// is starting to feel strange these days, but I do realize both are still used and your tool works with both as it should.

Very nice readme! And nice to see it has a man page. I would leave out the "It's simple:" line because that tends to make less confident people (like new people just learning) blame themselves if they have problems, and then instead of giving you feedback they'll give up and move on.

[nodesocket]

Great job. Small nitpick. Agree —domain should probably be called —url instead. Domain implies no scheme.

[bechampion]

as others said , dependecies need to be sorted. other than that i think this is quite cool and i will use it.

[jordache]

I suggest a convenient way to set cookie or auth headers. A lot of endpoints are behind authentication. The --req-headers flag is feasible, but there should be a shortcut flag just for authentication headers. Maybe --cookie and --auth ?

[trimstray]

https://github.com/trimstray/htrace.sh/issues/50

[trimstray]

ok, i'll add issue for this, thx.

[trimstray]

I'll update this project with your suggestions from this thread.

Thank you for your support!

[LinuxBender]

Here is a similar tool all contained in one shell script that only depends on openssl. [1] Albeit, a bit more verbose and doesn't have that nice one page output.

[1] - https://github.com/drwetter/testssl.sh

[password4321]

Also helpful, with zero dependencies (in PERL): https://github.com/portcullislabs/ssl-cipher-suite-enum

[sametmax]

Nice.

It's a step up from httpie, which is nice to craft requests, but not to check for security.

[bloopernova]

Looks really, really useful. Bookmarked, cloned, and shared with my team!

[trimstray]

Thanks. All suggestions/PR are welcome.

[chrisweekly]

Bookmarked, looks useful. Kudos!