# SOLVED: Named URL still show as generic page-2 **URL:** \ **Category:** RapidWeaver Classic\ **Created:** [December 16, 2021, 7:41pm UTC](https://forums.realmacsoftware.com/t/solved-named-url-still-show-as-generic-page-2/41775 "2021-12-16T19:41:36Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![sitebuilder](https://avatars.discourse-cdn.com/v4/letter/s/b77776/32.png) [@sitebuilder](https://forums.realmacsoftware.com/u/sitebuilder)\ **Post date:** [December 16, 2021, 7:41pm UTC](https://forums.realmacsoftware.com/t/solved-named-url-still-show-as-generic-page-2/41775/1 "2021-12-16T19:41:36Z")
Hi In the General Settings of each page, I changed the Browser Title and Folder to unique names. I saved the site, republished the whole site, and cleaned up my history yet I still see [website.com/page-2](http://website.com/page-2) and so on What should I do? SOLVED: I remembered I can only use lowercase letters (also: no spaces or nonstandard characters). ---
**Author:** ![Rovertek](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/rovertek/32/223_2.png) [@Rovertek](https://forums.realmacsoftware.com/u/Rovertek)\ **Post date:** [December 16, 2021, 8:22pm UTC](https://forums.realmacsoftware.com/t/solved-named-url-still-show-as-generic-page-2/41775/2 "2021-12-16T20:22:33Z")
Lower case is an option (at least on Apache). But spaces indeed must be replaced by hyphens or underscores. ---
**Author:** ![peterdanckwerts](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/peterdanckwerts/32/22443_2.png) [@peterdanckwerts](https://forums.realmacsoftware.com/u/peterdanckwerts)\ **Post date:** [December 17, 2021, 10:42am UTC](https://forums.realmacsoftware.com/t/solved-named-url-still-show-as-generic-page-2/41775/3 "2021-12-17T10:42:27Z")
I think it’s only domain names which are case-insensitive. Page and file names are case-sensitive – unless, I imagine, your webserver is running in case-insensitive mode (as my Mac is). ---
**Author:** ![Rovertek](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/rovertek/32/223_2.png) [@Rovertek](https://forums.realmacsoftware.com/u/Rovertek)\ **Post date:** [December 17, 2021, 12:50pm UTC](https://forums.realmacsoftware.com/t/solved-named-url-still-show-as-generic-page-2/41775/4 "2021-12-17T12:50:41Z")
I use both lower and upper case in my files naming—for example to differentiate between parent and child pages—and it works fine. ---
**Author:** ![peterdanckwerts](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/peterdanckwerts/32/22443_2.png) [@peterdanckwerts](https://forums.realmacsoftware.com/u/peterdanckwerts)\ **Post date:** [December 17, 2021, 2:11pm UTC](https://forums.realmacsoftware.com/t/solved-named-url-still-show-as-generic-page-2/41775/5 "2021-12-17T14:11:26Z")
All that indicates, I think, is that your webserver is set to be case-insensitive. It doesn’t mean that all are. [https://www.ibm.com/docs/en/sva/9.0?topic=configuration-support-urls-as-not-case-sensitive](https://www.ibm.com/docs/en/sva/9.0?topic=configuration-support-urls-as-not-case-sensitive) ---
**Author:** ![Rovertek](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/rovertek/32/223_2.png) [@Rovertek](https://forums.realmacsoftware.com/u/Rovertek)\ **Post date:** [December 17, 2021, 4:27pm UTC](https://forums.realmacsoftware.com/t/solved-named-url-still-show-as-generic-page-2/41775/6 "2021-12-17T16:27:41Z")
Thanks for the link. Strictly speaking, you are right. In the time of Web 1.0 lower case has been a must. Nowadays, case insensitivity on servers is widely used. I often see URLs of companies and publishing houses that use mixed cases. If your hosting server is not set for case insensitivity, use only lower case. Or, ask your host to configure their server for case insensitivity ---
**Author:** ![teefers](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/teefers/32/8173_2.png) [@teefers](https://forums.realmacsoftware.com/u/teefers)\ **Post date:** [December 17, 2021, 9:05pm UTC](https://forums.realmacsoftware.com/t/solved-named-url-still-show-as-generic-page-2/41775/7 "2021-12-17T21:05:11Z")
> [@Rovertek](#): > > you are right. In the time of Web 1.0 lower case has been a must. I beg your pardon. Case sensitive naming has been available on Unix servers since early on (pre Apache 1.0). Unix and its nephew Linux are “case- sensitive OS’s”. Windows, including IIS (the third most used web server), are not case-sensitive. The reason it’s still considered best practice to not mix cases for URI’s is constancy. The same reason we don’t put are shopping cart buried in the page’s footer or have our navigation midway down the page. It’s all about user experience. Users are used to websites being in lowercase. You mix cases in the URL and people will start getting 404’s. > Most pages on the Internet are going to be in all lowercase. When you create web pages, it’s best to always save all files as lowercase (including the file extension). > There’s a lot that you “can” do with URIs and URLs names. There are also lots that you “shouldn’t” do with these names. So let’s be clear on this. The domain name portion of the URL, left and including the top level name(.com, .org, .edu, .net), by specifications is case insensitive. That means that [EXAMPLE.COM](http://EXAMPLE.COM), [Example.com](http://Example.com), and [example.com](http://example.com) are all treated the same and translate to [example.com](http://example.com). The remaining part of the URL the path/filename “can” technically contain most characters you want , _including spaces_. This is a list of the _reserved_ characters(not including space) that has a special meaning when interpreting the URL/URI. If you want to use them, you will need to `%` encode them. It best practice not to use reserved them as part of the path/file name. ```auto : / ? # [] @ ! $ & ‘ ( ) * + , ; = ``` These character are considered Unsafe (including space). If you use them you will need to `%` encode them. ```auto “ < > % { } | \ ^ ` [] ~ # ``` You can also easily configure Apache to be case-insensitive. This would treat the entire URL path just like the domain name. `ABC`, `Abc`, and `abc` would be the same. Since most of us don’t have access to the httpd.ini file you can do that in the htaccess file: ```auto RewriteEngine On CheckSpelling On CheckCaseOnly On ``` This relies on the CheckSpelling Module being loaded. Most of the time, it is. If that doesn’t work, you can try this: ```auto RewriteMap tolowercase int:tolower RewriteRule ^(.*)$ ${tolowercase:$1} ``` Apache should automatically redirect all your URLs to lowercase ones. ---
**Author:** ![Rovertek](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/rovertek/32/223_2.png) [@Rovertek](https://forums.realmacsoftware.com/u/Rovertek)\ **Post date:** [December 18, 2021, 12:59am UTC](https://forums.realmacsoftware.com/t/solved-named-url-still-show-as-generic-page-2/41775/8 "2021-12-18T00:59:29Z")
Hey, Doug, Thanks for this clarification. As usual, your input is most thorough and accurate. I was hoping that you’d post before me… 👍 ---
**Author:** ![system](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/system/32/25301_2.png) [@system](https://forums.realmacsoftware.com/u/system)\ **Post date:** [January 17, 2022, 10:59am UTC](https://forums.realmacsoftware.com/t/solved-named-url-still-show-as-generic-page-2/41775/9 "2022-01-17T10:59:48Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.