1 [[!meta title="Problems with some scripts sites over the weekend"]]
2 Over the weekend we had some issues with content for
3 scripts.mit.edu virtual hosts/CNAMEs (\*.mit.edu sites, only not
4 \*.scripts.mit.edu sites) that had not requested a SSL server
5 certificate assigned to them. The issue mostly affected these sites
6 when accessed over SSL on port 444.
8 First, for a couple of minutes on Friday night, I made a change to
9 one of our web servers that accidentally caused requests to all
10 such sites to receive the content for axo.mit.edu (the
11 alphabetically first vhost with its own certificate). That change
12 did not reach the other server, and the misdirection was fixed as
13 soon as I realized my mistake.
15 However, this only fixed http and https, and did not take effect
16 for port :444. This was corrected earlier today after one of our
17 users reported it while testing a site that he had requested an SSL
20 I sincerely apologize for any trouble this may have caused.
21 Hopefully this did not affect many sites, because those intending
22 to use SSL should have a certificate, and sites with certificates
23 installed were not affected.