On my own web server (running nginx) I provide an HTTP 1.1 accessible
statistics service. It returns a single JSON structure with the underlying
packet statistics for the server and the current connection. Since this packet
is inserted into the HTTP 1.1 stream upon request, it provides both the
On Mon, 2 Mar 2015, Andrew Mcgregor wrote:
So, are you suggesting that, for example, Chrome's rather extensive network
debugging information get more publicised? We can probably arrange that.
That would be good. I have no idea what debugging info you are referring to.
David Lang_
On Tue, 3 Mar 2015, valdis.kletni...@vt.edu wrote:
On Mon, 02 Mar 2015 11:17:33 +0100, Mikael Abrahamsson said:
We have a huge amount of information in our TCP stacks that either are
locked in there and not used properly to help users figure out what's
going on, and there is basically zero inf
It's a heavy burden to place on ICMP ping to say that it should tell you about
all aspects of its path through all the networks between source and destination.
On the other hand, I'll suggest that Fred's point - treat ICMP Ping like any
other IP datagram with the same header options is the essen
