This is a known issue in IBM's 2.0.47 port of Apache (IHS), which was
fixed in a later upstream version (possibly by the 2.2.8 port, but I
really can't say for sure). It would take a lot of digging for me to
locate the specific version, so I'm going to pass on that one. At least
in my case, this
On Wed, Sep 9, 2009 at 1:48 PM, Houser, Rickhouser.r...@aoins.com wrote:
This is a known issue in IBM's 2.0.47 port of Apache (IHS), which was
fixed in a later upstream version (possibly by the 2.2.8 port, but I
really can't say for sure).
This message is not unique to IBM's Apache-based
