> -----Original Message----- > From: Robert Segall [mailto:[email protected]] > Sent: Tuesday, May 12, 2009 11:39 AM > To: [email protected] > Subject: [Pound Mailing List] Summary > > Hallo everybody > > I was away for a while, so I'd like to answer some of the > pending posts > here.
Welcome back! > - failed connections to back-ends and kill_be (Joe Gooch): > connecting to > a back-end is the cheapest check, certainly cheaper than > reading a page > and checking on its status. I fully agree that killing a > back-end should > be logged - we'll add that to the next release. Agreed. Though I think the suggestion of checking a page for status *only when deciding whether to resurrect or not* does have merit. When backends are loaded down, frequently they'll be erratic before they're stable again. (At least in my experience) http://users.k12system.com/mrwizard/pound/pound24.html has a LogBackendDeath patch if interested. > - autoconf dependencies (Thilo Bangert): we'll add -without-pcre, > --without-hoard, --without-tcmalloc in the next version. > > - case-insensitive URL matching: quite frankly, given that > you can do in > the regular expression itself, I don't see the benefit of adding a > configuration flag for that. (Since these go together) I wasn't aware of (?i) at all until it was posted here. It could be added to the man page (if it's not there already) since this seems to be a common thing. I'm still running Pound 1.9 in places... (yeah. Old) But the point is I believe up through 2.2, pound was case insensitive with url matching. So at the least, this is a paradigm shift. In addition, if compiled --without-pcre, would this (?i) option still be available? Or is it PCRE only? Seems like it might be worth having a consistent option, regardless of your library dependencies. http://users.k12system.com/mrwizard/pound/pound24.html has "NoCase" versions of URL and CheckURL directives that provide an alternate solution to a compile time option, with minimal code impact. For that matter, the more of those patches that go main-stream, the fewer I have to maintain. :) Thanks for your insight! Joe -- To unsubscribe send an email with subject unsubscribe to [email protected]. Please contact [email protected] for questions.
