Chris, Yeah I was thinking that the capture code would perfectly fit in some HTTP tunnel so that we can capture the whole thing coming out of the web server , what do you think ? Regards, Youssef
On Fri, Feb 20, 2009 at 5:38 PM, Christopher Schultz < ch...@christopherschultz.net> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Youssef, > > On 2/20/2009 9:27 AM, Youssef Mohammed wrote: > > I wanted actually to try this in the weekend, so lemme know if you need > some > > hand on that. > > I'm having some trouble with the response capture. It appears that > Tomcat itself fills-in some of the response headers either before or > after the first filter runs. For instance, the only header I see being > set is the Content-Length (which is explicitly being set by my > EchoServlet used for testing). > > Thus, I don't have access to the (default) status code (200 OK) and to > the following headers I can see coming back to the client: > > HTTP/1.1 200 OK > Server: Apache-Coyote/1.1 > Content-Type: text/xml;charset=UTF-8 > Content-Length: 44 > Date: Fri, 20 Feb 2009 15:28:48 GMT > > So, I think this might have to be implemented as a Valve, but I'm not > even sure that would be enough. I'm poking around in Tomcat's code to > see where those headers are set so I can determine the level at which > this is going to need to be done. > > It might come down to just using LiveHttpHeaders or Wireshark to do the > initial capture :) > > - -chris > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.9 (MingW32) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iEYEARECAAYFAkmezo8ACgkQ9CaO5/Lv0PDchgCgpfjSL+Rk3zGCCUSQwrPHUzTA > HQQAoKMkNqGUSzjPgW66Xiu94H14rT9n > =V+Nm > -----END PGP SIGNATURE----- > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > >
