[Codin]

I wish to share with you a problem I personally experienced recently when uploading a newly designed website to a small independent hosting company. Not all servers are set up the same. I have always used small letters when naming my html pages. I did not follow my usual pattern when I built my latest website. I submitted the site to the server using Filezilla FTP. The server would not except the pages because they were not small letters. I suggest using the following examples to name your web pages.

example.hml and not Example.html

also I do not know if you have had this problem with loading images or not. But many sites end up with broken image links or broken links to their pages. Usually this is a standard method to use to call your pics or gifs

<img src="img/1011.jpg" width= "175" height= "175" alt= "Brass Shell" />

. Well I found out recently some servers will not except your links to your images using small letters to spell out .jpg. Instead they insisted that the .jpg part of the link be as such

<img src="img/1011.JPG" width= "175" height= "175" alt= "Brass Shell" />

.I would suggest if you are going to be building websites and run into a problem of broken links I suggest you use Mozilla Firefox for a browser to check your site and use the developers toolbar. Mozilla exactly has an image tab on it's developers toolbar which will allow you to see how your images will display and will tell you the path used to load the images and also will tell you if you have and broken links to your images. I hope this will help Codin.

[Dormilich]

should I experience such problems, it would be a reason to switch the provider for me.

[drhowarddrfine]

Dormilich, on 24 October 2010 - 03:59 AM, said:

should I experience such problems, it would be a reason to switch the provider for me.

Agreed.

Also, the word he wants to use is 'accept' not 'except'. And the "toolbar" he speaks of is "Firebug".

[Atli]

Codin, on 22 October 2010 - 05:51 PM, said:

Well I found out recently some servers will not except your links to your images using small letters to spell out .jpg. Instead they insisted that the .jpg part of the link be as such

<img src="img/1011.JPG" width= "175" height= "175" alt= "Brass Shell" />

.

To be honest, that would be a deal-breaker for me. If the server required that the extension of a file, or the file itself, be a specific case (especially upper-case) I would throw it out instantly.

As far as I know, Apache respects the case of file names in the URI, but is not picky when it comes to extensions. Even using the wrong case in respect to the actual extension on the file is OK. - Windows based servers are the obvious exception, seeing as Windows is case-insensitive itself.

IIS and other Windows based HTTP servers *should* not put ANY restrictions on file names. Windows does not, so why would the server?

Linux based servers (Apache being the clear front-runner) *should* respect the case of file names, at least for file-systems that are case-sensitive themselves (which is most Unix servers). They could ignore extensions, but it wouldn't bother me if they didn't. - They should at the very least be case-insensitive like Windows servers.

But any server requiring you to put your file names or extensions in a specific case should be trashed immediately. (Who knows what other idiotic things that server does?!)