9

This question is broken because apparently the server side script tries to redirect the question to itself multiple times, since the question has an invalid utf-8 character in the title, it's stuck in an infinite redirect loop trying to correct its title, but fails.

Pronunciation and meaning of 

This is confirmed to be broken in the latest version of chrome and firefox under Windows 7 64-bit (Japanese version).

5
  • 3
    We are investigating; the utf-8 itself seems fine (code-point decimal 58619), so it is something more subtle. As I say: we're investigating. Frustratingly, it works perfectly on my local machine, so I can't repro conveniently. Thanks for reporting what is clearing an error. – Marc Gravell Oct 26 '11 at 23:15
  • @MarcGravell, FYI, I got "Content-Type:text/html; charset=us-ascii" in first response from server. Could that charset be issue? – YOU Oct 27 '11 at 2:16
  • 1
    @MarcGravell FYI, the first three HTTP request/response headers recorded by Google Chrome during the infinite loop. – ento Oct 27 '11 at 2:57
  • FWIW: wget "japanese.stackexchange.com/questions/1472/…" loops as well. Full log at: pastebin.com/vNy6unYj – Axioplase Oct 27 '11 at 5:01
  • @Axioplase ultimately that's the same question, so that isn't unexpected – Marc Gravell Oct 27 '11 at 9:53
6

It looks like this is a bug in IIS (the underlying Microsoft web-server product that hosts all these sites). If you really want the gory details, see this stackoverflow question: https://stackoverflow.com/questions/7913830/is-iis-performing-an-illegal-character-substitution-if-so-how-to-stop-it. For now, I will add a defensive check on this particular sequence, but we are pursuing the issue with Microsoft (and with the horde of stackoverflow users).

clarification: this is now filed with Microsoft; for now, we have a workaround in place so that the question is reachable.

1

You must log in to answer this question.

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