3

The following link doesn't parse correctly on StackOverflow website.

http://msdn.microsoft.com/en-us/library/ms724947(VS.85).aspx

It breaks on the '(' character, it seems.

2
  • It seems that it breaks here too.
    – user133490
    Aug 11 '09 at 16:41
  • 1
    Well, geez, this is only the 500th time this has been brought up. Excellent.
    – GEOCHET
    Aug 11 '09 at 16:42
4

It seems like I just recently discussed this very issue:

I doubt we'll get this fixed, but you can resolve it yourself by URL encoding ( and ) as %28 and %29. Since one of these bugs gets posted every two to three days, here's a simple rule of thumb:

Any characters in your URL other than A-Z, a-z, 0-9, and /.=?-+%&* (and the : in "http:") should probably be URL encoded.

I've cobbled together a quick page that will encode the things that shouldn't need encoding. You can find it here. It doesn't use any jQuery, so it's probably completely unreliable. If you find anything it should be encoding but isn't, let me know.

5
  • 2
    it is fixed now, we basically force-encode it for everyone Aug 14 '09 at 6:11
  • I'm not sure this is fixed:- stackoverflow.com/questions/762692/… Looks fine in the edit preview, but not in the answer page (using firefox). Tried different formats, encoding the '#' character, with no luck. Sep 17 '09 at 2:07
  • @brass-kazoo: You are correct: it was encoding # when it should have left it alone. But the actual problem in that answer is that you left the http:// off of the link to andariel, which was screwing things up. I've edited your answer to fix that. Sep 17 '09 at 11:39
  • 1
    @Jeff Atwood: this still fails on SO!
    – Lazer
    May 9 '10 at 19:30
  • @eSKay we don't support that in comments, see meta.stackexchange.com/questions/49201/… May 9 '10 at 23:58

You must log in to answer this question.

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