Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 158 Stack Exchange communities.

What is meta?
Here's how it works:
  1. Any Stack Exchange user can ask a question
  2. The community provides support, votes on ideas, and reports bugs
  3. Your voice helps shape the way Stack Exchange operates

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
share|improve this question
Occurs on Stack Overflow, Server Fault and Super User, as well as other SE sites. – Michael Hampton Jul 2 '13 at 21:08
We know; Top Men are working hard to fix it... – Shog9 Jul 2 '13 at 21:09
Totally killin my workflow – Aaron Blenkush Jul 2 '13 at 21:09
Thanks, was just about to post this too. Hopefully, the 'Top Men' will post what when wrong - that would be cool to know. – michaellindahl Jul 2 '13 at 21:10
Crap. Now I have to work. – jason Jul 2 '13 at 21:10
Who broke it this time? balpha – bluefeet Jul 2 '13 at 21:11
@Shog9 DevOops. – Michael Hampton Jul 2 '13 at 21:11
Might be a server fault. – Old Checkmark Jul 2 '13 at 21:11
@doubleDown: Or a stack overflow. – jason Jul 2 '13 at 21:12
if they do not know how to fix it, they should ask at stackoverflow – Gaby Jul 2 '13 at 21:12
Benjamin's Meta rep just skyrocketed for this post. – Corion Jul 2 '13 at 21:13
Amazing... Stack Overflow goes down and programmers world wide take a synchronized break. – Aaron Blenkush Jul 2 '13 at 21:15
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 '13 at 21:15
I wonder how much one minute of this costs Stack Exchange, Inc. BUT NO PRESSURE GUYS – Pëkka Jul 2 '13 at 21:17
Is it normal to be comment-vote-capped on meta? – Jan Dvorak Jul 2 '13 at 21:26
up vote 39 down vote accepted

This was my fault.

The offending code was:

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

What should have been is

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

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).

share|improve this answer
Way to go, Slash... – Aaron Blenkush Jul 2 '13 at 21:22
sure... blame it on the RegEx so noone gets it – CSᵠ Jul 2 '13 at 21:26
@kaᵠ looooooool – Ihsan Jul 2 '13 at 21:26
I thought that on Meta, if you do something bad, you get downvoted :) – chue x Jul 2 '13 at 21:28
@chuex But he fixed it too! – ɥʇǝS Jul 2 '13 at 21:29
this is part of the move to SSL sweet. – Pëkka Jul 2 '13 at 21:31
You should probably tag the question status-complete now.. – ɥʇǝS Jul 2 '13 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 '13 at 21:38
@Seth Or close it, like every other "site down for 10 minutes" post – Michael Mrozek Jul 2 '13 at 21:39
Shouldn't the pattern be "^https?://"? Only match the beginning? ;) – zch Jul 2 '13 at 21:39
You sure RegEx is (needed|the best choice) here? – CSᵠ Jul 2 '13 at 21:43
@JonathanHobbs silver, according to team rules you have to throw 500k exceptions to get a gold, I only went a little over 200k this time. – Nick Craver Jul 2 '13 at 23:16
@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 '13 at 3:05
It wasn't your fault. It was balpha's. – Emrakul Jul 3 '13 at 6:21
@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 uses another CDN, and also doesn't exhibit the problem. – Nick Craver Jul 3 '13 at 18:05

You must log in to answer this question.

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