Case-Sensitive conflicts in Short Links
Peter Lafford
I was surprised to find that the Short Links system allowed me to create a short link "/AaaBbbb", while there was already another link "/aaabbbb", and it did not warn me of the conflict.
However, the system is apparently case-sensitive, but at the same time, it is NOT case-sensitive. That is, if you type in lower case a URL that has CAPS, and there is NOT a matching lower-case URL, it will take you to the URL that was created with CAPS and lower case. So, the link "/XXyyyy" can be reached by typing the URL as either "XXyyyy" OR "xxyyyy" .
But to reach MY "/AaaBbbb" you must type it exactly. If you type "/aaabbbb" it goes to the lowercase URL; if you type "/Aaabbbb" it does NOT find a case-matching URL so it defaults to the lower-case short link.
Shouldn't the system disallow URL's which conflict by virtue of case?
