On 13/08/2010, at 01:32, James Pearson wrote: > Shouldn't we not have to do that, as we don't know when someone will use > capital letters, and thus use the case-insensitive match on every rule?
Yeah, you have a point there. > Then again, perhaps it's something that Cherokee shouldn't have to deal with, > anyways (other than how it currently does), and we should just file bugs > against Android's browser. In an ideal scenario Cherokee wouldn't have to deal with the issue. In this case, the problem is obviously introduced by Android's browser. However, independently of who is to blame here, we ought to make Cherokee ready to deal with the all the real situations. I guess the best option is to modify the default host name comparison so it runs in case-insensitive mode from now on. -- Octality http://www.octality.com/ _______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
