Re:HTTP/2 Frequently Asked Questions
by FooBarWidget on Friday October 03, 2014 @09:11AM
(#8405346)
Human-readable is only a matter of tooling. Why is HTTP human-readable? Because you have a lot of tools that understand ASCII. Without them, HTTP is just as unreadable to you as any other stream of bytes.
[ Parent
| on HN ]
Re:HTTP/2 Frequently Asked Questions
by protonfish on Friday October 03, 2014 @11:16AM
(#8405877)
True, but it doesn't undermine my point. You can troubleshoot HTTP 1.1 with common, generic tools. How do you work with HTTP2? I have no idea.
When I'm debugging HTTP, 98% of the time it's either with curl, Wireshark, or by dumping state in my own server-side code. Things like curl will work just the same. Wireshark has an HTTP/2 plugin; given their history, I'm sure it'll be excellent by the time there's much HTTP2 in the wild. And anybody writing server-side code is hacking together their own tools anyhow.
The rare occasion where this will be a big difference for me is telnetting to port 80 and typing HTTP by hand. Honestly, I only do that out of habit; I can do the same things just as well with curl. But even when HTTP/2 ships, I'm sure it will be at least a decade before servers stop supporting HTTP/1.1. Probably longer. So I'm not expecting this to make a big difference to my debugging habits.
Re:HTTP/2 Frequently Asked Questions
by FooBarWidget on Friday October 03, 2014 @11:42AM
(#8405992)
The tools don't exist right now, but they will become available. Existence of tooling follows demand. HTTP 2 has a large momentum so tooling will exist.