10-21-2015 04:22 AM
I think domain.com should be considered subset of *.domain.com. There are lots of web pages presenting the content in both with and without www prefix. Putting 2 different filter for the same domain is just stupid.
Is there any workaroud?
10-21-2015 05:09 AM
Can you clarify more about the domain that you are trying to access/allow.
domain.com is not a subset of *.domain.com that is correct. Because *.domain.com say there should be something in place of * like abc.domain.com
You have to add
domain.com--> May not be required but try
domain.com/
*.domain.com/
*.domain.com--> May not be required but try
10-21-2015 07:41 AM
Hi Ramazan
the reasoning behind this is that these are regex expressions rather than a DNS lookup or direct db match. the dot in between the asterisk and the domain name is counted as a character in regex, the absense of a dot before the former forces regex to match only a domain without prefix
hope this helps
Tom
10-21-2015 02:42 PM
As reaper notes, the period becomes part of the match criteria. If you really don't want to have the two entries you can use the asterik without the period.
*domain.com
But keep in mind this also matches different domains that end with the same text:
otherdomain.com
10-22-2015 02:01 AM
IMO it needs a feature request for domain entries so you don't have to enter it twice.
IE: "domain:google.com"
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!
