Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 153 Stack Exchange communities.

What is meta?
Here's how it works:
  1. Any Stack Exchange user can ask a question
  2. The community provides support, votes on ideas, and reports bugs
  3. Your voice helps shape the way Stack Exchange operates

Here is an example: ->


If you edit this question you'll see that both urls display in the preview - but the second one mixed-case which is not standards-compliant is (correctly IMO) eliminated in the 'live' version.

share|improve this question
How bizarre. HtTp:// ... – Matt Jan 26 '12 at 11:54
When I read the title of the question I thought it an unlikely scenario, but with only the first letter capitalized, I can see how this could happen. – Oded Jan 26 '12 at 12:18
@Obed, yes it did happen too on I used HtTp in the title as I was worried that Http would not be processed as odd by the average human brain. Mine didn't for a while though admittedly my brain is a little below average :-) – Jack Douglas Jan 26 '12 at 12:33
The client-side sanitizer uses case-insensitive regular expressions where the server-side one doesn't, which is easily fixed, but there may have been good reason for that. Even then, the client-side sanitizer leaves behind the URL as plaintext, so I'm unsure what the server-side is doing that causes it to be removed completely... – Tim Stone Jan 26 '12 at 12:55
@TimStone: autolinking in our Markdown versions happens by enclosing bare links in <http://anglebrackets> if they aren't, and then converting links in angle brackets to actual links. Since the server doesn't consider it a valid link, the <Http://foobar> stays as it is, and to the sanitizer, it looks like an HTML tag that gets killed. – balpha Jan 26 '12 at 13:12
@balpha Ohhhh, that makes sense. I see the difference in DoAutoLinks now. :) – Tim Stone Jan 26 '12 at 13:18
The RFC says For resiliency, programs interpreting URLs should treat upper case letters as equivalent to lower case in scheme names (e.g., allow "HTTP" as well as "http"). -- so I guess it's okay to allow mixed case. Of course we should do it consistently. – balpha Jan 26 '12 at 13:21

You must log in to answer this question.

Browse other questions tagged .