-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 16 Aug 2006, at 12:11, beno - wrote:
Instead of continuing to stab in the dark, which you have been doing
the whole time, you need to spend the time to get familiar with the
tools you are using and with basic troubleshooting techniques.
Wonderful, Jens. So, what do you suggest? I would have thought
Z2.py and/or the error logs would help me out here, but they
aren't. Apparently, these aren't the tools I should be using, but
what are if these aren't??
You're still not reading or understanding what people tell you to do.
It's like talking to a wall.
I suggested using network traffic analysis with e.g. ethereal to
analyze the traffic between your server and the problematic client's
browser.
Other posters also suggested browser tools like Mozilla/FireFox
LiveHTTPHeaders and similar products for IE to analyze headers that
are sent back and forth between the problematic browser and your server.
jens
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)
iD8DBQFE40c2RAx5nvEhZLIRAhfJAKCFAZtCMThnwcQG2wZ+tfnMKzuimwCeKD2e
gtsSTqkY4rbue48mLjLXVm4=
=0kcZ
-----END PGP SIGNATURE-----
_______________________________________________
Zope maillist - Zope@zope.org
http://mail.zope.org/mailman/listinfo/zope
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope-dev )
