case sensitive folders

When I create a fold in FWPro5 and use capital letters, the link to those pages require the URL to be entered as capital letters. Why is that?

ex: site.com/FOLDER vs site.com/folder


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

On 23 May 2008, 5:04 pm, Beatrice wrote:

When I create a fold in FWPro5 and use capital letters, the link to those pages require the URL to be entered as capital letters. Why is that?

ex: site.com/FOLDER vs site.com/folder

Because your Web server is probably running some form of Unix on a case-sensitive filesystem. There are case-insensitive filesystems out there (your Mac, for one) but in the server space, it’s all very literal and what you type is what you get. (Or not, as you have seen.)

Walter


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

I have confirmed that my web server (hosted at ServerLogistics) is definitely case sensitive. This is becoming a problem because more and more sites are linking to pages on our websites with an otherwise correct URL, except the case is wrong. That of course results in a browser error.

I spoke with ServerLogistics about this, and they recommended I read the following page that talks about edits to the .htaccess file:

Being brain dead to code, I wasn’t sure what to make of the discussions there, but the “RewriteMap” code seemed easy enough so I added the following to my .htaccess file in the root (/public_html) directory on my server:

RewriteEngine on
RewriteBase /
RewriteMap insensitive tolower:
RewriteRule ^[/]*(.*)$ /${insensitive:$1} [R,L]

Unfortunately, immediately after I added the above code to my .htaccess file, I got Internal Server Error 500 messages on every single page in my domain! I then quickly deleted that code, save my .htaccess file, and then all was well.

I reported back to ServerLogistics on this, and they said they would investigate what other code might work. Since they are searching for the solution just as I am, I thought I would tap the advice of the experts on this list.

Any ideas?

Many thanks,

James Wages


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

It is a monumentally difficult question, I know, but I would love to hear the thoughts of you code experts on this.

Thank you.


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

According to Apache, mod_rewrite categorically can’t do this. If you can get Aaron to enable mod_speling, that should fix things for you.

Walter

On Jul 15, 2010, at 8:36 PM, “JDW” email@hidden wrote:

It is a monumentally difficult question, I know, but I would love to hear the thoughts of you code experts on this.

Thank you.


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

Walter, I sincerely appreciate your input.

But according to the web page I link to above…

Use mod_speling to force the correct capitalization
of filenames and directories. 
This requires "real" filenames.

What concerns me about that is the ‘real filenames’ comment. Because mod_speling is merely a filename spell checker, right? In such a case, would a mere spell-checker help to change the “case” of my filenames, especially when many of my filenames are actually product model numbers or combined words with no space between them or truncated terms, like this?:

1440b.html
1370s.html
lm100.html
contactus.html
legalinfo.html
bat_faq.html

Thank you.


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

No. Real means that the filename maps to a real file, as opposed to virtual filenames, like the ones in the FreewayTalk site. You should be fine, no matter what your files are named, as long as they actually exist on your server.

Walter

On Jul 15, 2010, at 9:38 PM, “JDW” email@hidden wrote:

Walter, I sincerely appreciate your input.

But according to the web page I link to above…

Use mod_speling to force the correct capitalization
of filenames and directories. 
This requires "real" filenames.

What concerns me about that is the ‘real filenames’ comment. Because mod_speling is merely a filename spell checker, right? In such a case, would a mere spell-checker help to change the “case” of my filenames, especially when many of my filenames are actually product model numbers or combined words with no space between them or truncated terms, like this?:

1440b.html
1370s.html
lm100.html
contactus.html
legalinfo.html
bat_faq.html

Thank you.


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

Thank you for the clarification, Walter.

I had ServerLogistics enable mod_speling on our server. I then added the following code to the .htaccess file in the root directory for each of our sites:

<IfModule mod_speling.c>
CheckSpelling on
</IfModule>

If mod_speling is enabled, then one only needs to add “CheckSpelling on” to the .htaccess file, but the IF statements ensure that the entire site won’t suddenly become inaccessible should mod_speling ever get Disabled.

The URL case sensitivity problem is now solved. Perfect!

Thank you, Walter!

–James Wages


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options