http://hathaway.freezope.org/Software/TCPWatch
--On Dienstag, 25. Februar 2003 11:24 +0100 Romain Slootmaekers
[EMAIL PROTECTED] wrote:
Yo,
searching the zope site and googling yielded too many data and no info,
so I might as well ask it here.
We are very interested in finding out the exact
Andreas Jung wrote:
http://hathaway.freezope.org/Software/TCPWatch
Apparantly, I forgot to mention this:
proxying isn't an option either.
You can't just, on the fly, put a proxy between several components in a
production setup.
Sloot.
--On Dienstag, 25. Februar 2003 11:24 +0100 Romain
Clemens Robbenhaar wrote:
Hi Romain,
Yo,
searching the zope site and googling yielded too many data and no info,
so I might as well ask it here.
We are very interested in finding out the exact HTTP Responses that the
zope server pushes towards the client.
So is there a low
On Tuesday 25 February 2003 12:08 pm, Romain Slootmaekers wrote:
We need this in our 3th line support, were we want to be able to follow
all ins and outs for singled out user (fi filtered on cookie).
We also need to be able to turn this on/off at runtime.
I would do this in the front-end
Are you mainly concerned about the http headers in the response, or the
response body? If it is just the headers, Squid's log_mime_hdrs feature
will log all HTTP headers from both the request and response for you for
each request. If nothing else, perhaps it's a start...
Sean
-Original
