3 ms·
Whoa, so Google Chrome is now talking SPDY to www.google.com ? I had no idea. Anyone know a good way of running a packet sniffer on OS X so I can see it in act
by simonw 16y ago
Whoa, so Google Chrome is now talking SPDY to www.google.com ? I had no idea.
Anyone know a good way of running a packet sniffer on OS X so I can see it in action?
- mdxch 16y agochrome://net-internals/#spdy
- deleted 16y ago[deleted]
- snprbob86 16y agoWow! When they removed the "http:// http:// from Chrome, I knew exactly why they were doing it: to hide the SDPY rollout while simultaneously not breaking copy paste interop with non-Chrome uses. However, I had no idea they had already done it! Amazingly clever and effective. I totally saw it coming and then totally missed it's arrival. Awesome.
- mbelshe 16y agoNo, this is pure conspiracy theory. :-) The decision to drop "http:// http:// from the display was a UI decision and had nothing to do with the internals. The idea is that the "http:// http:// is just user-confusion. Most users can't spell HTTP, much less know why it is there. Why do we subject our poor users to it? Personally, I don't care. Chrome does not recognize "spdy://" as a protocol scheme, and the UI display changes nothing with respect to how chrome selects protocols.
- JonnieCache 16y agoWireshark works just fine on OSX. http://wireshark.org http://wireshark.org or brew install wireshark
- throw_away 16y agoIn terminal: sudo tcpdump -s3000 -X -i en1 port 80 switch to -i en0 if you're using your ethernet, or you have a macbook air.