==> This issue has been fixed <==

For historical benefit:

On the user's page (SO, SF, meta, ...), if you type "T.J" (no trailing dot) in the search box you'll see names starting with "T.J" ("T.J. Crowder", "T.J. Boberek", "T.J.", etc.) but if you type "T.J." (with the trailing dot, as one normally would) nothing happens. At all. The currently-displayed results don't change (as opposed to showing no matches).

(Related but different bug: Users Search box doesn't find names with an apostrophe ')

  • @dup voter: It's not an exact duplicate, it's (as I said) related but different. His symptom is different from mine, for a start (I'm not talking about mine being a dot and his being an apostrophe, the actual symptom -- what happens -- is different). (@all: the dup voter chose the question I linked as the dup) – T.J. Crowder Feb 23 '10 at 9:17
  • Given S.Mark's filter URL, this seems to be related to Trailing periods produce a server level 404. – Arjan Apr 3 '10 at 12:16
  • Dude, you better change your name :) – uɐɯsO uɐɥʇɐN May 14 '10 at 23:14
  • As another dotted user, I second this bug. – C. Ross Jul 1 '10 at 10:44

I've debugged with Firebug, and I noticed that when I search for T.J. it returns the following error:

Server Error in '/' Application.

The resource cannot be found.

Description: HTTP 404. 
The resource you are looking for (or one of its dependencies) could have been removed, had its name changed, or is temporarily unavailable.  
Please review the following URL and make sure that it is spelled correctly. 

But, when I search for T.J. Crowder, it's just fine.

So, it happens when the searched name ends with a dot.


afaik windows has problems with names that end in a dot. so using ntfs-3g in linux to create a directory named cannot_open. and then trying to open it from windows will result in an error »directory does not exist« (or something similar, it's been some time since i've used windows with such a folder)


This issue has been fixed. I don't know when, but it doesn't happen anymore, so...

  • I think upgrading to .NET 4 fixed this. They addressed a lot of dumb legacy ASP.NET limitations on URLs.. – Jeff Atwood Sep 16 '10 at 8:03

You must log in to answer this question.

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