Can we quickly identify what else was broken to roll out 2.0.52 in the next day or two? I presume this too was 2.0.51 specific?
Bill >jorton 2004/09/22 01:57:30 > > Modified: . Tag: APACHE_2_0_BRANCH STATUS > Log: > Find a third 2.0.51 regression THIS WEEK and win a FREE subscription > to [EMAIL PROTECTED] OFFER ENDS SOON. > > + *) Another ap_rgetline_core fix. > + > http://cvs.apache.org/viewcvs.cgi/httpd-2.0/server/protocol.c?r1=1.152&r2=1.153 > + +1: jorton
