16

While reading through a question here on Meta, I saw this question listed under the Related section. Gritting my teeth and clicking the link resulted in a whirlwind of redirects and an error in Google Chrome.

The webpage at Please append the reason for closing to the title along with "Closed" has resulted in too many redirects. Clearing your cookies for this site or allowing third-party cookies may fix the problem. If not, it is possibly a server configuration issue and not a problem with your computer.

Visiting the URL directly has the same effect. Clearing cookies did not help.

The offending loopy title reads:

Please append the reason for closing to the title along with "[closed]"

I've seen similar questions asked with regards to migrated questions, so perhaps this is a dupe, but I'm not sure. What might cause this?

I'm using Chrome 16.0.912.77

Screenshot of endless 301 redirects

7
  • Hum. Can't repro now, though could repro 28 mins ago.
    – Mat
    Feb 4, 2012 at 18:49
  • Nah...same here. No-repro at the moment. Perhaps an update happened in the mean time?
    – Bart
    Feb 4, 2012 at 18:51
  • 3
    It's something to do with having "[closed]" in the title. Robert Harvey changed it to "closed" to fix it Feb 4, 2012 at 19:30
  • I feel like I should vote to close only so that I can find out who is the person who wants this well written bug report closed Feb 9, 2012 at 18:43
  • 1
    @Koper It was I. With my massive fingers on my mobile phone I accidentally managed to vote to close (and confirm <-- yes, massive idiot) on my own question. :) But in any case Robert Harvey confirmed that the title was the cause of the problem. So it could be closed if he doesn't answer here.
    – Bart
    Feb 9, 2012 at 19:04
  • Although I would of course like to see the answer/explanation.
    – Bart
    Feb 9, 2012 at 19:13
  • Here's another one: meta.stackexchange.com/questions/6737/…
    – Shog9
    Mar 22, 2012 at 5:03

2 Answers 2

9

Turns out that we had 5 questions on Meta and 6 question on Stack Overflow that were like %[[]closed]%.

We already have a sanity check that ensures you do not add the word [closed] to the title, turn out our redirect logic was tripping for legacy posts that were created prior to the sanity check.

I am pretty apprehensive of playing with any redirect logic, fixed the offending rows in the DB.

1
  • Sorry to bring this up after such a long time, but perhaps you have some input: The same issue was brought up in this question for another SE site. Is the editing procedure you have followed general practice (and should the question perhaps be asked on the SE's specific Meta) or it there any point in requesting a global SO/SE-wide fix?
    – Bart
    Jun 25, 2012 at 10:38
7

Confirmed:

enter image description here

Chrome 16.0.912.77 m on Windows 8

5
  • A downvote for confirming a bug? Feb 4, 2012 at 19:34
  • 2
    +1 For your help in confirming I've not lost my sanity. ;)
    – Bart
    Feb 4, 2012 at 19:39
  • And a close vote on the question itself - odd indeed. +1 from me. Feb 9, 2012 at 18:24
  • @AdamRackis Don't worry. The (accidental) close vote was mine. See my comment above.
    – Bart
    Feb 9, 2012 at 19:36
  • Maybe someone envy you for already using Windows 8? ;) Mar 22, 2012 at 7:12

You must log in to answer this question.

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