A meta.SE bug came up which also applies to SOFU.

Any URL path ending in a dot produces a low-level server 404, rather than the usual SO 404, even when the dot is part of a string which is supposed to be ignored.

Shouldn't the URLs be sanitized before they are processed so that special characters are treated as literals?

closed as off-topic by Ilmari Karonen, Martijn Pieters, Josh Crozier, hims056, Lucifer Jan 19 '14 at 12:16

This question appears to be off-topic. The users who voted to close gave this specific reason:

  • "The problem described here can no longer be reproduced. Changes to the system or to the circumstances affecting the asker have rendered it obsolete. If you encounter a similar problem, please post a new question." – Ilmari Karonen, Martijn Pieters, Josh Crozier, hims056, Lucifer
If this question can be reworded to fit the rules in the help center, please edit the question.


I believe this is a bug deep, deep in the .NET framework. Seriously.


How to create a Uri instance parsed with GenericUriParserOptions.DontCompressPath

and related connect item, System.Uri incorrectly strips trailing dots


  • 2
    Are we inventing [status-framework-fault]? – Tyler Carter Mar 30 '10 at 3:02
  • 1
    [status-byframeworkdesign] – Gnome Mar 30 '10 at 3:55

This bug has been fixed. Now:

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