Hello Keith, Thanks! Did those off the top of my head, just before going to bed, and thought I had forgotten something. I believe your additions are correct, and probably better than what we're actually using.
Bob Menschel Wednesday, June 15, 2005, 7:51:52 PM, you wrote: KI> Robert Menschel wrote: >> SARE has been playing around with URI rules lately, and when we need >> to test for something in the host/domain area, we use something like: >> >>>uri rule_name m'(?:https?://)?[^/]*testgoeshere' KI> I think you want a ^ at the start of your regex. As it is, that will KI> match any string with "testgoeshere" anywhere in it, since the match can KI> start at the "t" rather than at the beginning of the string. >> In other words, the test must precede any/all slashes except for those >> that might be within http:// >> >> When we need to test for something after the host/domain area, we >> reverse that, like: >> >>>uri rule_name m'(?:https?://)?.+/testgoeshere' KI> For this I think you want something like KI> uri rule_name m'^(?:https?://)?[^/]+/.*testgoeshere' KI> Without the ^ anchor and without changing . to [^/], you'll match things KI> like 'http://testgoeshere.invalid/path', because the 'http://' part of KI> the regex is optional. And without adding .* after the slash, you won't KI> match things like 'http://example.com/atestgoeshere' -- but maybe you're KI> not wanting to.
