[Chilli] uamdomain / uamallowed

[David Bird]

Well, since the option is "uamdomain", I think we can assume the "user"
is thinking "uamdomain" plus "*.uamdomain" ... so, we change the logic
to fix the issue of '*uamdomain' (as it is always now) to being:

(assuming 'question' is the hostname being resolved)

if question equals uamdomain exactly OR
   question is longer than uamdomain and ends with ".uamdomain"

So that "google.com" will match "google.com" or "*.google.com". 

As for using regex for matching, I'm thinking of making it only for use
with a new compile time option --enable-domainfile which will allow the
loading of bulk regex based "dynamic walled garden" domain names. 


On Thu, 2010-11-11 at 14:19 +0200, Johan Meiring wrote:
> On 2010/11/11 02:08 PM, Wichert Akkerman wrote:
> > On 11/11/10 13:06 , Johan Meiring wrote:
> >> On 2010/11/11 01:13 PM, Henk Kleynhans wrote:
> >>> I'm happy for uamdomain="google.com" to mean
> >>> google.com and all subdomains, as it currently is.
> >>>
> >>> And for uamdomain="mail.google.com" to only
> >>> refer to mail.google.com
> >>
> >> How must chilli know that "google.com" is a domainname and
> >> "mail.google.com" is a hostnname?
> >
> > It can't - DNS has no concept of 'hostname' or 'domain'.
> >
> 
> Therefore having "google.com" include subdomains and "mail.google.com" not 
> include subdomains is impossible.
> 
> Suggesting .google.com for subdomains again....
>