case-sensitive

I haven't been able to find a straightforward answer to this, which leads me to believe that it's something really really simple. Either way, here I go. All of the calls in my $routeProvider work great, but are case sensitive. Here's a code sample: config(function ($routeProvider) { $routeProvider. when('/', { controller: 'TmpCtrl', templateUrl: '/app/home.html' }). when('/foo', { controller: 'TmpCtrl', templateUrl: '/app/foo.html' }). otherwise({ redirectTo: '/' }); }); What do I need to add so that '/Foo', '/fOO', '/FoO', etc, all redirect to the same path? There is an option you can pass to

My server is Case Sensitive, and id like to turn it to inSensitive. Example of what I mean is lets say I upload Fruit.php Well then going to this file wont work: www.website.com/fruit.php but this one will: www.website.com/Fruit.php Is there a way so Fruit.php and fruit.php will work? also with the directories. i.e: / S cript/script.php /script/ S cript.php Case sensitivity depends on the file system, not Apache. There is a partial solution, however. mod_rewrite can coerce everything to lowercase (or uppercase) like so: RewriteMap tolowercase int:tolower RewriteRule ^(.*)$ ${tolowercase:$1}

I have a set of variables I allow some people I work with to edit. These are True ( T ) and False ( F ) values, but I have some people that insist on putting t and f instead of the upper case values respectively. I use the following workaround code to properly set uppercase values: IF '%dotnet35%'=='f' set dotnet35=F IF '%dotnet35%'=='t' set dotnet35=T IF '%dotnet40%'=='f' set dotnet40=F IF '%dotnet40%'=='t' set dotnet40=T IF '%regedit%'=='f' set regedit=F IF '%regedit%'=='t' set regedit=T IF '%SSL%'=='f' set SSL=F IF '%SSL%'=='t' set SSL=T This is however extremely bulky and it's not easy on

.NET's HttpSessionState using an " InProc " store seems to treat session variable key values as case insensitive. For example: session["foo"] = 1; session["Foo"] = 2; Trace.Write(session["foo"].ToString()); // => 2 This behavior appears to be undocumented, so I'm wondering if it is simply a side-effect of the underlying session store mechanism, or intentionally implemented by the class itself. Since C# treats everything else as case-sensitive, it is a bit unnerving for the session to not act the same way. What gives? Does it differ by store type? Is it there for backwards-compatibility with VB

I'm trying to write a "suggestion search box" and I cannot find a solution that allows to highlight a substring with javascript keeping the original case. For example if I search for " ca " I search server side in a case insensitive mode and I have the following results: Calculator calendar ESCAPE I would like to view the search string in all the previous words, so the result should be: Ca lculator ca lendar ES CA PE I tried with the following code: var reg = new RegExp(querystr, 'gi'); var final_str = 'foo ' + result.replace(reg, '<b>'+querystr+'</b>'); $('#'+id).html(final_str); But

I personally do not like programming languages being case sensitive. (I know that the disadvantages of case sensitivity are now-a-days complemented by good IDEs) Still I would like to know whether there are any advantages for a programming language if it is case sensitive. Is there any reason why designers of many popular languages chose to make them case sensitive? EDIT: duplicate of Why are many languages case sensitive? EDIT: (I cannot believe I asked this question a few years ago) This is a preference. I prefer case sensitivity, I find it easier to read code this way. For instance, the

I'm writing an abstraction function that will ask the user a given question and validate the answer based on a given regular expression. The question is repeated until the answer matches the validation regexp. However, I also want the client to be able to specify whether the answer must match case-sensitively or not. So something like this: sub ask { my ($prompt, $validationRe, $caseSensitive) = @_; my $modifier = ($caseSensitive) ? "" : "i"; my $ans; my $isValid; do { print $prompt; $ans = <>; chomp($ans); # What I want to do that doesn't work: # $isValid = $ans =~ /$validationRe/$modifier; #

I'm trying to scrape META keywords and description tags from arbitrary websites. I obviusly have no control over said website, so have to take what I'm given. They have a variety of casings for the tag and attributes, which means I need to work case-insensitively. I can't believe that the lxml authors are as stubborn as to insist on full forced standards-compliance when it excludes much of the use of their library. I'd like to be able to say doc.cssselect('meta[name=description]') (or some XPath equivalent) but this will not catch <meta name="Description" Content="..."> tags due othe captial D