8

The page https://stackoverflow.com/users/122299/ result in Firefox saying that

Firefox has detected that the server is redirecting the request for this address in a way that will never complete.

Indeed, some investigation shows the page to redirect to itself, while my page, https://stackoverflow.com/users/126214/ redirects to https://stackoverflow.com/users/126214/lennart-regebro

Thus I suspect that this user, who has no ascii character in his name, has triggered a small bug. :)

User Details on http://data.stackexchange.com alt text

5
  • Nice catch, it'll be interesting to know what happened there!
    – Benjol
    Jan 7, 2011 at 9:51
  • I don't believe it has anything to do with the presence of ASCII chars in the display name - I just changed my Meta display name to my Chinese name, and I believe you should still be able to access it.
    – Yi Jiang
    Jan 7, 2011 at 10:04
  • Hmm, it's working now. Just fixed I guess. :) Jan 7, 2011 at 10:07
  • Yup, working again. Jan 7, 2011 at 10:10
  • Jeff Atwood saiz: '<waves hands> there are no bugs'
    – Yi Jiang
    Jan 7, 2011 at 10:16

1 Answer 1

2

We no longer attempt to redirect when the name slug is empty.

4
  • It seems like this bug has found its way back: chinese.stackexchange.com/users/67/… Dec 15, 2011 at 7:53
  • (it does not work even if I remove the display name, eg: chinese.stackexchange.com/users/67 ) Dec 15, 2011 at 7:54
  • @null during private beta things work differently because access is restricted. If it is a problem when the site is public, then let us know. Dec 15, 2011 at 8:08
  • The issue NullUserExceptiom reports was simply a code bug related to the switch-over to the new user profile, and would affect all sites that use international URL support (on user profiles), and was not just because of the private beta. It got fixed a few days ago. Dec 17, 2011 at 11:24

You must log in to answer this question.

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