A previous patch did not allow it to be runtime configurable and Graham (correctly) noted that what made the most sense regarding bogus headers was in the eye of the beholder.
In general, however, 1.3 is more "robust" in handling these bad headers since it basically send back the headers seen up to the bad one... NOTE: the patch isn't in final form yet, but want to know if the direction is such that it has a shot of being not-vetoed :) Bill Stoddard wrote: > > > > This patch adds a directive > > Do we really need a new directive? I just have this general unease at the > number of new config directives we have been creating lately... > > Bill > -- =========================================================================== Jim Jagielski [|] [EMAIL PROTECTED] [|] http://www.jaguNET.com/ "A society that will trade a little liberty for a little order will lose both and deserve neither" - T.Jefferson
