Re: A proposal for an HTTP stream capture mechanism

>> What kind of info are dumped? Content and/or headers? > > What is dumped is the entire stream, byte for byte, captured at the TCP > socket level. So, includes request, headers and body. Both ways. Is it easy to read? Thanks Max

hg: jdk7/tl/jdk: 6832557: TEST_BUG: java/lang/Class/getEnclosingConstructor/EnclosingConstructorTests.java fails to compile

Changeset: 057e4afcf978 Author:alanb Date: 2009-04-23 19:44 +0100 URL: http://hg.openjdk.java.net/jdk7/tl/jdk/rev/057e4afcf978 6832557: TEST_BUG: java/lang/Class/getEnclosingConstructor/EnclosingConstructorTests.java fails to compile Reviewed-by: darcy, mcimadamore ! test/java/la

Re: A proposal for an HTTP stream capture mechanism

Max (Weijun) Wang wrote: Hi Jessie This is very useful. What kind of info are dumped? Content and/or headers? What is dumped is the entire stream, byte for byte, captured at the TCP socket level. So, includes request, headers and body. Both ways. This is supposed to complement the traditio

Re: A proposal for an HTTP stream capture mechanism

Hi Jessie This is very useful. What kind of info are dumped? Content and/or headers? Can you also capture the connection info? Sometimes I need to know if a new connection is created or the old one is reused. The \. in sun\.com looks a little cumbersome. I know .hgignore supports several

A proposal for an HTTP stream capture mechanism

I have been working on adding better logging and debugging tools to the HTTP implementation. A significant chunk of the bugs that we have to investigate are HTTP related and being able to monitor the traffic has always been a problem. Using a packet sniffer is cumbersome and not always possible.