9

When I try to visit this question on meta.SE, I get a server error (HTTP 500).

It has been migrated away to meta.SO, where I can look at it without a problem.

It also works if I visit the question with the noredirect=1 parameter. So I guess something with the redirection handling is messed up.

The revision history and the timeline here on meta.SE don't show any error.

3
  • Yeah, the logic that looks up the destination URL assumes the destination URL starts with "http://"... HTTPS ruins everything.
    – Shog9
    Commented Mar 14, 2017 at 23:17
  • https-bugs-everywhere?
    – enderland
    Commented Mar 14, 2017 at 23:19
  • 2
    You get an https bug, you get an https bug, every-body-gets-an-https-bug!
    – Catija
    Commented Mar 14, 2017 at 23:20

1 Answer 1

5

var result = record.Comment.Substring(record.Comment.IndexOf("http://"));

This is why we can't have nice things.

A quick fix is out in prod now, but we (well, Nick Craver) will be looking at switching up how we track migrations to avoid this sort of direct string parsing.

You must log in to answer this question.

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