Scott Beuker wrote:
Please let me know if there is anything more I can do. I hope this helps.
I thought about writing a small example script myself but given the amount
of time I have spent on this issue already, I have to be careful here at
work.
A little extra information that may help to narrow it down; I sniffed the HTTP sessions to the server and got a copy of the headers in each of a working and non-working computer. I did not see any differences of significance so I was going to try changing the various fields one at a time to figure out which caused it not to work, by telneting into the server and then sending the query manually.
Instead what I found was that the headers in the http request do not matter, it seems to simply be a matter of what client computer you are coming from. When I pasted in the request of a machine that did not work from a machine that works, it did still work, and vice versa.
yike, that's not a good sign.
unfortunately, it also limits our ability to help. we can only do so much investigation when we can't reproduce an issue - if you can't reliably reproduce it across your own machines it's even harder.
Unfortunately for me, given this information I have hit the
end of the troubleshooting I can do.
one way to help would be to start stripping away your environment, piece by piece. for instance, start by removing all non-essential processing from your script, then by removing excess httpd.conf so that you just have enough to run one request, and all that request does is something that exhibits the bug.
then try reproducing that httpd.conf and script within Apache-Test. you can use this as a starting point.
http://perl.apache.org/~geoff/bug-mp2.tar.gz
if you can boil everything down so that anyone can untar test, run it, and reproduce it, we'll be much more likely to be able to fix it.
I know it sounds like a lot. sorry :)
--Geoff
