Yea, I saw that late last night after digging through the manual. I had setup all ~100 or so of my sites using the wildcard, guess I got some work to do. :-)
On Sun, Oct 24, 2010 at 11:43 AM, Alvaro Lopez Ortega <[email protected]>wrote: > Hello Dennis, > > On 23/10/2010, at 20:39, Dennis Clayton wrote: > > > I checked 2 other of my sites running on IIS 6 & 7 using my Android > browser and IIS disregards the case and the sites both come up fine with any > combination of upper/lower case. So far in my testing, it only seems to be > an issue when using the Android web browser, Opera Mini lowercases the URL > before requesting the page. > > > > I guess for now, I'll add a few different cases to my virtualhost and > perhaps submit a bug report after I get some additional opinions. > > We documented the issue a few weeks ago¹. Basically, the workaround is to > use Regular Expression matches with a prefix that forces the evaluation to > be performed in case-insensitive mode: > > ========== > Hint: Although it is rare, there are some web-broswsers out there that do > not seem to convert the FQDN to lowercase before sending the requests. This > mainly happens with built-in browsers or very-early implementations. Even in > those cases it is possible to have case-insensitive host matching by using > regular-expression matching. For example, if you’re domain name was > Example.com and were dealing with one such browser, you would have to > prepend (?i) to your regular expression. That in turn would perform a > case-insensitive evaluation, effectively solving the problem. > > The followgin Case-insensitive RegEx matches both example.com and > Example.com > > (?i)example.com > ========== > > 1.- http://www.cherokee-project.com/doc/config_virtual_servers.html > > -- > Octality > http://www.octality.com/ > >
_______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
