For diagnostics I'd prefer something like Paros, Burp or WebScarab, which has a graphical interface, but this one seems to offer a quite nice scripting API which I'll have to take a closer look at.
The textual interface is actually a curses-based interface that lets you do stuff as you would normally do in paros, such as capture a request or edit a request and replay it. So it is not just like you're watching logs. You can take many kinds of actions from within that text interface, and very quiclky. The scripting API is also very good.
It lets you use Connect compatible middleware to alter the request or response - (https://github.com/mdp/middlefiddle/blob/master/.middlefiddl...)
There's a bunch of these proxies out there, and they all provide something different, but if you're just looking to inspect the HTTPS request, I'd also recommend the excellent Charles Web Proxy - http://www.charlesproxy.com/ - I bought a copy years ago, and it's been invaluable.
If you're a company that relies on virus scanning HTTP traffic then the increasing number of websites which force SSL looks like a potential problem.