Last week we installed pound on a new server. We found that our regular
expressions, which worked with an older verion of PCRE, were no longer
working. On our old box, with PCRE version (4.5), the regular
expressions were doing case-insensitive checks. The new box, with PCRE
6.6, is doing case-sensitive checks.
We use RedHat linux here, and I don't remember if PCRE was built
locally, or a package was used, but whatever the case, our URL matches
were no longer working correctly. We use windows boxes behind pound, so
we never really want to do case-sensitive checks, and I guess were lucky
that we didn't have this problem before.
To make our pound.cfg work on the new box, I had to put "(?i)" in each
of our checks (around 50 in all). I'd like to see pound support an
global directive or compile-time flag for case-sensitivity checks. Any
thoughts?
Sebastiaan van Erk wrote:
If you've got PCRE compiled in you could use (?i) to turn on caseless
matching. From the PCRE manpage:
An option change within a subpattern (see below for a description
of subpatterns) affects only that part of the current pattern that
follows it, so
(a(?i)b)c
matches abc and aBc and no other strings (assuming PCRE_CASELESS is
not used).
Regards,
Sebastiaan
Peter Zsigmond wrote:
Hi,
Do you guys know a way to make my url matching case-insensitive? I'm
working with a bunch of windows webservers and the requests I'm getting
are all mixed up.
Thanks,
Peter
--
To unsubscribe send an email with subject unsubscribe to [email protected].
Please contact [email protected] for questions.
--
To unsubscribe send an email with subject unsubscribe to [email protected].
Please contact [email protected] for questions.
--
To unsubscribe send an email with subject unsubscribe to [email protected].
Please contact [email protected] for questions.
