'When URL Contains' bug?

[tanstaafl]

Hi Eric,

Seems there is a bug - or it doesn't work the way I expect...

I just decided to start auto-populating some things in anticipation of the new functionality that is coming, and discovered this...

I administer some Mailman lists, and have an Account set up in PWM for logging in.

I was doing some testing that wasn't related to PWM, and set up 3 accounts that all point to the same primary domain of the same domain (testing character sets to debug an authentication problem with postgreSQL). So, what I have is:

Acct1
When URL Contains: .mydomain.com/mailman
Use This URL: mydomain.com/mailman

Acct2
When URL Contains: .mydomain.com/
Use This URL: mydomain.com

Acct3
When URL Contains: .mydomain.com/
Use This URL: mydomain.com

Acct4
When URL Contains: .mydomain.com/
Use This URL: mydomain.com

The problem is, when I enable auto-populate on all 4, and load the ".mydomain.com/mailman" URL, auto-populate prompts me to choose between all 4 accounts, when the other 3 do NOT have the /mailman in the 'When URL Contains' field.

So, apparently, it only does *partial* matching on the contents of this field?

[tanstaafl]

Never mind... I see where my thinking was fuzzy...

Sorry for the false alarm.

I look forward to the 'When URL EQUALS' option... ;)

[Eric H. Jung]

Ideally, the When URL Contains field should be configurable to:

• When URL Contains
• When URL Equals
• When URL Starts With
• When URL Ends With
• Matches User-specified Regular Expression

And, of course, it should accept multiple entries.