Re:HTTP 2.0
by peterwwillis on Tuesday July 09, 2013 @02:07PM
(#6014145)
The nc example is the last bastion of this argument. But what about SSL? For a long time you just couldn't test it, or maybe use OpenSSL's server feature piped to nc.
But now nc supports SSL natively, making it super easy. Just as it will support binary HTTP natively, making it super easy. And everyone will finally stop caring about ASCII.
Re:HTTP 2.0
by BHSPitMonkey on Tuesday July 09, 2013 @02:03PM
(#6014111)
Should your willingness or unwillingness to use a tool for these (rare) scenarios influence the design of the protocol in any substantial way?
Just because I use Charles or Wireshark doesn't mean that I only want to use those specialized tools. I have definitely been in situations where I'm doing something like running nc as a proxy and looking at raw HTTP. I wouldn't choose to throw that away and revert to the bad old days without a big win.