topic URL filtering thinks domain.com is not a subset of *.domain.com in General Topics

URL filtering thinks domain.com is not a subset of *.domain.com

ramazan.polat — Wed, 21 Oct 2015 11:22:11 GMT

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?

Re: URL filtering thinks domain.com is not a subset of *.domain.com

pankaku — Wed, 21 Oct 2015 12:09:21 GMT

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

Re: URL filtering thinks domain.com is not a subset of *.domain.com

reaper — Wed, 21 Oct 2015 14:41:42 GMT

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

Re: URL filtering thinks domain.com is not a subset of *.domain.com

pulukas — Wed, 21 Oct 2015 21:42:37 GMT

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

Re: URL filtering thinks domain.com is not a subset of *.domain.com

cpainchaud — Thu, 22 Oct 2015 09:01:48 GMT

IMO it needs a feature request for domain entries so you don't have to enter it twice.

IE: "domain:google.com"