Posted By Prasad Maduranga on 21 Feb 2021 02:57 AM
It is not allowing me to post the code what I want. I tried several times. Anyway just check this atleast.

IgnoreCase="False" .....

i do have my own rewrite rules on the server, but didn't think that dnn implemented that site setting in that section. perhaps it saw that i have a section and failed to update it - maybe a feature or a bug. but i can certainly manually add it.

also, your Imported Rule 1 appears in the email notification, but not in the posting on the site. 

this rule is probably the secret sauce. thank you. i will post later my results.

Posted By tony bonn on 21 Feb 2021 11:20 AM

Posted By Prasad Maduranga on 21 Feb 2021 02:57 AM
It is not allowing me to post the code what I want. I tried several times. Anyway just check this atleast.

IgnoreCase="False" .....

i do have my own rewrite rules on the server, but didn't think that dnn implemented that site setting in that section. perhaps it saw that i have a section and failed to update it - maybe a feature or a bug. but i can certainly manually add it.

also, your Imported Rule 1 appears in the email notification, but not in the posting on the site. 

this rule is probably the secret sauce. thank you. i will post later my results.

 

 

this episode has been interesting and frustrating, but i may have the matter resolved. the server's url rewrite module has an out-of-the-box rule for forcing urls to be lower case. it actually works, but with a penalty. when i try to save page name changes in dnn, it returns an error stating that http get is not allowed on this resource. so i disabled the rule on the server, made my name changes, but discovered that they remained lower cased without the rewrite rule. 

unforutately, i have so much caching going on that i am not convinced that the change is enduring. so i will monitor it for the next couple of days to months to see if the conversion holds.

the moral of the story is that the dnn feature may or may not work, but you can always create a re-write rule in the url rewrite module on the server. as of now i am able to name my pages with mixed case, eg About, and the url address in the browser shows /about, and the menu on the page shows About. so far so good. i need to make sure that this good fortune is not the result of lingering caching.

the story is not over. apparently some caching was in play. when i ran checkbot, it was able to go to a mixed case url. enabling the server rule fixed it. however, in a classic case of whack-a-mole, checkbot also penalized me severely for having redirected pages.

so here is the way this needs to be supported, which is my next endeavor. 1. pages must be created with lower case names so that redirection is not required. 2. the menuing system must support mixed case names for aesthetic reasons. as of now, i don't know that dnn supports this need. maybe my 3d party theme has a menuing system where i can map the page url (lower cased) to a visual representation of it using an arbitrary name (mixed case).

so as an example, i should be able to create a page named about, but have it display in the menu as About. the default behavior for menus is to take the page name, ie about, and then show it as about.

For those ending up on this thread through google:
In newer versions of DNN (this is 09.13.07) you can use these options:

The first one converts the urls in the menu to lowercase, the second redirects any incoming urls to the lowercase variant.
HTH

Nice! We had a client enable and use these settings recently.  I've honestly not gotten huge gains from these settings in recent years.  Google seems to be more than capable of figuring out the difference.  However, after going through that recently, I realized that you can also break various features/modules when changing these settings.  

If you modify these settings, be sure to check all mission-critical features on your site.  If your custom/third-party extensions aren't taking these settings into account, some features may break.  (I'm not telling you to not do this.  I am only telling you to be sure to test thoroughly after applying the settings.)  

@Will: True but I noticed that Google Search Console does "complain" about multiple urls to the same page due to mixed case urls support

I believe the lowercase vs uppercase scenario is more from an end user perspective, having the first letter of each word in your URL will make things easier for end users than having everything in lowercase. Creating friendly URL's it's always a good approach!

Google has more than 20 years trackig down URL's worldwide, I don't think they have a problem with lowercase vs. uppercase.

Another scenario where you can see different URL's for the same web page (just like Timo mentioned) its on GA4 speciallly if you've localization enabled. 

Posted By Marco Alvarado on 1/24/2025 6:02 PM

I believe the lowercase vs uppercase scenario is more from an end user perspective, having the first letter of each word in your URL will make things easier for end users than having everything in lowercase. Creating friendly URL's it's always a good approach!

Google has more than 20 years trackig down URL's worldwide, I don't think they have a problem with lowercase vs. uppercase.

Another scenario where you can see different URL's for the same web page (just like Timo mentioned) its on GA4 speciallly if you've localization enabled. 

Whatever setting you have, IMO DNN should take case in consideration.

It's weird that

www.mysite.com/products

www.mysite.com/Products

www.mysite.com/PRODUCTS

All resolve the same page.

2 of these should 301 to the other one IMO

Canonical URLs FTW!  😎