Reading over the bug I'm still curious about the actual "race condition" aspect of it... Even doing an 'OPTIONS *' "right before" sending the request does not ensure that the race condition goes away because there is still that period of time where the backend could go away right after that (in fact, it also complicates things since we need to worry about the keepalive aspects)...
The best solution is to simply trap that error and have Apache "do the right thing", which is what r645813 does. Ruediger and I tested his patch @ ApacheCon and it works pretty well. On May 12, 2008, at 1:52 PM, Adam Woodworth wrote:
Hi, I was wondering if anyone might have some more information on bug #37770. I've added a comment there recently, at the end of the bug report, #83. https://issues.apache.org/bugzilla/show_bug.cgi?id=37770 I think this bug is a serious issue for our application so I'm trying to see if anyone has figured out a good way to actually fix this problem. The patch mentioned in #82 is not a fix for the actual problem caused by the race condition. Sounds to me like this race condition can't really be solved though...does anyone know what other proxy software does in these cases with keepalive connections? Cheers, Adam
