It's not sending a valid SSL cert for that but I know it may be not easy to configure so. I propose to point them to another IP, then disable https on that IP.
Version: unspecified
Severity: minor
Description
Description
Details
Details
- Reference
- bz43265
Event Timeline
Comment Actions
Disabling HTTPS is worse than simply giving an invalid certificate (Which is really perfectly secure, but untrusted because it's for the wrong domain), so I propose WONTFIXing this.
Comment Actions
This is an ops decision, but I would also recommend a WONTFIX for this. If we point to another IP, where https is disabled, then they would get an error saying the server isn't available. The cost of issuing www. certificates for every language is also prohibitively high.
Comment Actions
Either adding www,en.wikipedia.org as alternative name (but we have www.*.wikipedia.org!), or wontfixing.