Case-sensitivity
From Well Designed Urls WiKi
music ringtones discount lisinopril metal ringtones samsung ringtone free cellular ringtones tv ringtone actos buy cialis ultracet online discount lortab free sony ericsson ringtones latin ringtone order cialis discount wellbutrin phendimetrazine online download sexy ringtones sagem ringtone sony ericsson ringtone free toques ringtones cheap norco jazz ringtones download vocal ringtones buy clonazepam amitriptyline online free love ringtones skelaxin zovirax online buy tenuate christian ringtone cheap ionamin cheap buspar free verizon ringtones download tmobile ringtones buy metformin darvocet cool ringtone cheap paxil discount actos animal ringtone diethylpropion online free true ringtones buy xenical free country ringtones order ortho fly ringtone free talking ringtones cheap provigil cheap darvon download sprint ringtones order amoxicillin cheap metformin download true ringtones lorazepam cheap ringtone free monophonic ringtones mobile ringtone discount ultracet free mtv ringtones buy flexeril buy atenolol norvasc online cheap ephedrine home mortgage loans discount phentermine buy carisoprodol darvocet online albuterol online buy ultracet order pharmacy online cheap norvasc discount prozac glucophage cheap vigrx cipro online texas holdem poker cheap flexeril download motorola ringtones tmobile ringtones buy phendimetrazine sildenafil online free humour ringtones cheap ambien cheap lipitor cheap nexium telus ringtones discount fioricet rave ringtones buy zithromax buy norco effexor online free tv ringtones wwe ringtone free vocal ringtones clonazepam online student loan clomid online wwe ringtones order lorazepam lipitor cheap flonase baspascboa This page is for information about URLs and Case-sensitivity
Contents |
Mike Schinkel's Opinion
In my current opinion HTTP URLs:
- SHOULD NOT BE case-sensitive. Users really don't understand the distinction between a URL like URL #1. and URL #2. and it is rarely if ever necessary.
- SHOULD HAVE their Authority [1] and Path [2] in all lower-case like URL #1.
- SHOULD issue a Permanent (301) Redirect to the lower-case equivalent whenever a URL is requested that contains upper-case characters like URL #2.
- SHOULD NOT change the case of Querystring parameter values (i.e. Do not coverted "Yes" in URL #3. to lower-case.)
- CAN have their parameter names lower-cased but it won't affect anything either way (i.e. "Print=" CAN be coverted to lower-case in URL #3. to look like URL #4. if desired.)
- CAN have their Fragment [3] lower-cased but it doesn't have to be (i.e. "#Summary" CAN be coverted to lower-case as in URL #7. to look like URL #8. if desired.)
I am continuing to do research on this subject and plan a signifcant blog post article at blog.welldesignedurls.org.
Example URLs
-
http://www.example.com/my-topic/ -
http://www.example.com/My-Topic/ -
http://www.example.com/my-topic/?Print=Yes -
http://www.example.com/my-topic/?print=Yes -
username@www.example.com:8888 -
http://username@www.example.com:8888/my-topic/?print=Yes -
http://www.example.com/my-topic/#Summary -
http://www.example.com/my-topic/#summary -
http://www.example.com/my-topic/?print=Yes#summary
External Links
Footnotes
[1] - The Authority for URLs on the public web is just the Domain (i.e. www.example.com). Sometimes the Domain can be suffixed by a Port (i.e. :8888) and much more rarely prefixed by a Userinfo (i.e. username@). In the rarest of cases the Authority would look like that in Example #5.; see URL #6. for that Authority included in a complete and valid URL.
[2] - The Path starts with the first "/" if there is one and ends with "?", "#", or the end of the URL (i.e. /my-topic/ in URLs #1, 3, 4, 6, 7, 8, & 9 and /My-Topic/ in URL #2.)
[3] - The Fragment comes after the "#" and typically allows the browser to just to a specific location in a Web Page.

