Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 158 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

I recently posted an answer on stackoverflow that rendered perfectly in the editor preview, but in the posted text the links all got gobbled up: links were stretching across multiple lines where they shouldn't, from another the url showed up directly in the posting. A friendly fellow on SO then simply replaced the offending url with one that provides the same text on another server, and the problem was gone. The offending url was

To see the posting in question check this answer, look for the initial version of it.

share|improve this question
Dupe: – random Aug 1 '09 at 9:37
up vote 2 down vote accepted

Funnily enough, the choke move you're talking about has been brought up before and was recently floated back to the front page of questions by Community.

In short, the editor will not parse embedded links well and the cause for your error/edit.

share|improve this answer
Isn't that a bit of a lame answer?! For one thing, the editor preview is rendering the links fine, so there is a part of the system that can handle those links. For another, I can see no technical reason why you shouldn't be able to handle any link, since they are always clearly delimited, and the system doesn't have to parse them from free text. I even tried to embed the links directly with HTML <a href="..."></a>, and it failed. At least this should work for any URL. Is SO, a technicians site, saying "You cannot provide arbitrary URLs because we cannot get our CMS to handle them"?! – ThomasH Aug 1 '09 at 10:07
Looks like they/we/you are. – random Aug 1 '09 at 11:00

We now encode any ":" chars that occur past a certain position in the URL so this should work.

share|improve this answer
Yeah, that's what I know now. Try figuring that out when you have five links in your post and no idea which one is causing the mess... – ThomasH Aug 1 '09 at 16:34
I checked, and the ":" should in fact be escaped. So http%3A// should be a valid alternative to the URL shortening services. I will try this next time :-). – ThomasH Aug 3 '09 at 21:28

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .