In the "when URL contains" box is "deckertechnology.net"
In the "use this URL" box is "http://deckertechnology.net"
Ok, just fyi, there is a security issue that has been discussed
here, which details why this is almost backwards from the way you should use these fields.
In this particular case, the most secure way would be:
When URL contains: /deckertechnology.net/ <- note the trailing slash
Use this URL: deckertechnology.net
I guess this is a good example of a potential issue using the technique described in the above thread that I use:
.domain.com/
If you use this now, and go to a URL that doesn not have the www. preceding the top-level domain name, then it would consider that NOT a match.
What I'm hoping to convince Eric to do is code this so that it recognizes a true sub-domain and/or sub-directory from a fake, automatically. So, in effect, all you'd have to enter in the first field is 'deckertechnology.net', and PM would evaluate it thusly:
*[.]deckertechnology.net[/]*
where the preceding '.' (dot) is the only character allowed (but not required) to immediately precede what is entered, and the trailing '/' (slash) is the only character allowed (but not required) to follow the last character entered, and the asterisks are, of course, wildcards (anything).
Anyway, the thread makes good reading to understand just how these fields are used, and how their behavior may possibly change (for the better).