82

I hope the staff can see this question, not sure if I will once I post.

enter image description here

Update: This does not happen on meta, this happens in programmers, and in StackOverflow. Happens in meta-programmers too.

If this helps you, here are the response headers.

HTTP/1.1 500 Internal Server Error
Cache-Control: private
Content-Type: text/html; charset=utf-8
X-Frame-Options: SAMEORIGIN
Date: Tue, 02 Jul 2013 21:09:39 GMT
Content-Length: 18814
50
  • 8
    Occurs on Stack Overflow, Server Fault and Super User, as well as other SE sites. Jul 2, 2013 at 21:08
  • 19
    We know; Top Men are working hard to fix it...
    – Shog9
    Jul 2, 2013 at 21:09
  • 18
    Totally killin my workflow Jul 2, 2013 at 21:09
  • 4
    Thanks, was just about to post this too. Hopefully, the 'Top Men' will post what when wrong - that would be cool to know. Jul 2, 2013 at 21:10
  • 61
    Crap. Now I have to work.
    – jason
    Jul 2, 2013 at 21:10
  • 5
    Who broke it this time? balpha
    – Taryn
    Jul 2, 2013 at 21:11
  • 12
    @Shog9 DevOops. Jul 2, 2013 at 21:11
  • 7
    Might be a server fault. Jul 2, 2013 at 21:11
  • 7
    @doubleDown: Or a stack overflow.
    – jason
    Jul 2, 2013 at 21:12
  • 28
    if they do not know how to fix it, they should ask at stackoverflow Jul 2, 2013 at 21:12
  • 9
    Benjamin's Meta rep just skyrocketed for this post.
    – Corion
    Jul 2, 2013 at 21:13
  • 14
    Amazing... Stack Overflow goes down and programmers world wide take a synchronized break. Jul 2, 2013 at 21:15
  • 9
    How many of the entries in the exception log are caused by people repeatedly pressing F5 to see all of the random images?
    – Brant
    Jul 2, 2013 at 21:15
  • 11
    I wonder how much one minute of this costs Stack Exchange, Inc. BUT NO PRESSURE GUYS
    – Pekka
    Jul 2, 2013 at 21:17
  • 7
    Is it normal to be comment-vote-capped on meta? Jul 2, 2013 at 21:26

1 Answer 1

39

This was my fault.

The offending code was:

Path.Combine("/Content", Regex.Replace(ContentPath, "https?://sstatic.net/","/"))

What should have been is

Path.Combine("/Content", Regex.Replace(ContentPath, "https?://sstatic.net/",""))

This meant that the second result which should be something like stackoverflow was coming out at /stackoverflow. When you feed that to Path.Combine(), you get /stackoverflow and not /content/stackoverflow...and that path is very wrong for a load that has to occur when rendering the editor.

If you couldn't tell - this is part of the move to SSL (which is now live in our test environment, stay tuned).

23
  • 18
    Way to go, Slash... Jul 2, 2013 at 21:22
  • 12
    sure... blame it on the RegEx so noone gets it
    – CSᵠ
    Jul 2, 2013 at 21:26
  • 1
    @kaᵠ looooooool
    – Volkan
    Jul 2, 2013 at 21:26
  • 5
    I thought that on Meta, if you do something bad, you get downvoted :)
    – chue x
    Jul 2, 2013 at 21:28
  • 1
    @chuex But he fixed it too!
    – ɥʇǝS
    Jul 2, 2013 at 21:29
  • 11
    this is part of the move to SSL sweet.
    – Pekka
    Jul 2, 2013 at 21:31
  • 1
    You should probably tag the question status-complete now..
    – ɥʇǝS
    Jul 2, 2013 at 21:36
  • Should any of us happen to meet a physicist on an island, we'll refer to this as "The Incident."
    – landons
    Jul 2, 2013 at 21:38
  • @Seth Or close it, like every other "site down for 10 minutes" post Jul 2, 2013 at 21:39
  • Shouldn't the pattern be "^https?://sstatic.net/"? Only match the beginning? ;)
    – zch
    Jul 2, 2013 at 21:39
  • @MichaelMrozek Close it as what, now that TL is gone?
    – ɥʇǝS
    Jul 2, 2013 at 21:41
  • 1
    You sure RegEx is (needed|the best choice) here?
    – CSᵠ
    Jul 2, 2013 at 21:43
  • 3
    @NickCraver Not trying to be offensive, but is there any QA/Testing going on before pushing these changes? This is the fourth time in 10 days that something unit testing should have caught made it to production. Seems like if anyone should know development practices, it should be the Stack Overflow crew.
    – Chris S
    Jul 3, 2013 at 3:05
  • 2
    It wasn't your fault. It was balpha's.
    – user206222
    Jul 3, 2013 at 6:21
  • 1
    @ChrisS almost always we test locally, in dev, and on meta before it goes live. The specific problem here is that local and meta do not use the CDN, and do not exhibit the problem...dev uses another CDN, and also doesn't exhibit the problem. Jul 3, 2013 at 18:05

You must log in to answer this question.

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