-----BEGIN PGP SIGNED MESSAGE----- According to mattmurphy@kc.rr.com: > Workarounds [...] While those workarounds are ok in principle, it should be noted that this bug (CAN-2003-0245) has been fixed in Apache 2.0.46 published about two weeks ago. Instead of applying any workaround an update to the latest Apache version is recommended. Regards... - -- Lars Eilebrecht - The Apache Software Foundation lars@apache.org - http://www.apache.org/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iQCSAwUBPuTvQT6Pt/L4g0HZAQENYwPnYLC/RZTPINjCiY8v4tRS+7To7JBgUXjL GZVxeay/0Nmw/oSa6U2DT+ajlswXYZB9fs7BniSM5wiqsg4x/gt4ZZAGsnbwP+Up p1CFte/SzwUmAIOYPFkCfv22nHiAg953cDc7YOhIKDjW4sWcGblMEXKA84qly6DQ BUd8IOo= =qoCl -----END PGP SIGNATURE-----