4 ms·
This forum appears to have an invalid certificate: Domain: forums.getpebble.com CN = *.vanillaforums.com If you use HTTPS Everywhere, you'll want to uncheck
by Someone1234 12y ago
This forum appears to have an invalid certificate:
Domain: forums.getpebble.com
CN = *.vanillaforums.com
If you use HTTPS Everywhere, you'll want to uncheck this specific site, remove the HTTPS part of the URL and reload.
PS - I love HTTPS Everywhere but it always surprises me just how many sites have broken HTTPS implementations.
- jackweirdy 12y agoAnd surprises me how few SSL-deploying sysadmins use HTTPS Everywhere! (Or perhaps, how few browse their own site...)
- hluska 12y agoI'm getting the sense that QA means something dramatically different to the web developers of today...Seldom a day goes by when I don't find major errors (that I would fire people for not catching) on major web apps!!
- tekromancr 12y agoYea, but sometimes it's impossible to offer TLS. Like, in this case, where a forum software is being hosted remotely, and they are putting a custom domain in front of it. Squarespace is another notable example. These services simply DON'T offer ssl support when used with custom domains. You really can't expect everything to work right when you aren't even offering the service that is being requested, can you?
- yellowapple 12y agoThat's because quite a few of us shunt the folks trying to access port 80 back onto port 443 (usually by redirecting the request to the https:// https:// equivalent, be it in the load balancer, in the web server, or (in some cases) in the application/site itself). The world's switching to HTTPS-only setups anyway (particularly when deploying JSON APIs, which are all the rage nowadays). Might as well be ahead of the curve.
- the_mitsuhiko 12y agoMany websites do not support HTTPS but have no chance to disable the default listener that is in place because it comes from somewhere else.
- JohnTHaller 12y agoThis is the whole reason the site itself doesn't direct you to https or advertise it is available. In order to support https, you don't just install a cert, you know. You have to make sure your whole chain supports it. Including things like third party CDN providers, which can be more expensive to enable https than you pay for the CDN. So, if you use an extension that randomly directs you to connect using a method the site operator never told you to use, expect problems.
- Someone1234 12y ago> This is the whole reason the site itself doesn't direct you to https or advertise it is available. They are advertising it. They have a web-server running on 443 open to the public, they aren't required to, but they choose to. They're also erroneously returning status code 200 (instead of 404 or 301). > So, if you use an extension that randomly directs you to connect using a method the site operator never told you to use, expect problems. Nothing "random" about it. The site advertises that it has HTTP running on 80 and HTTPS on 443. So I have an extension which opts for 443 when status code 200 is returned as a first priority and then 80 as a backup. Google and Bing's search results do exactly the same thing. If they don't want people to use HTTPS/443 then simply shut it down, problem solved. If you have to have 443 running for another site then return status code 404 (or 301).
- X-Cubed 12y agoThere is no reason that HTTP and HTTPS ports have to serve the same website. In this case, the HTTPS port is serving pebble.vanillaforums.com (or whatever) while the HTTP port is serving forums.getpebble.com. The HTTPS port could just as easily be serving up an admin page for the forums, rather than the forums themselves.
- Too 12y agoThe site operator never told me to use plain http either. I just "randomly" ended up there by clicking on a link on HN that has no relation at all with the site. If you expect http->https redirection to be the only valid path to a https site, then a MITM attacker would obviously disable that redirection because it's still done on the unsecure channel. This is the whole reason extensions like https everywhere exists.
- kbenson 12y agoJust because the same IP address also listens on port 443 doesn't mean that delivers the same website, and assuming it does is not a failure on their part, it's a failure of assumptions you or some software you utilize (knowingly or not) has made along the way.
- Someone1234 12y agoIndeed it doesn't. So why are they returning status code 200? > not a failure on their part, it's a failure of assumptions you or some software you utilize No, it is a failure on their part. They're returning the wrong status code. The software I utilize checks that, they got it wrong. Return 404 instead.
- kbenson 12y agoYou misunderstand the situation. It's entirely valid to serve one site on port 80 and another on port 443. Consider this scenario: A webserver listening on a specific IP on port 80 and serving HTTP traffic, but using name based virtual hosting (reading the Host: header) to determine what site to deliver. We'll say it's configured for emample1.com and example2.com. The same webserver (or a different one, it doesn't matter) listening on that same IP, but port 443, and serving HTTPS traffic. Without use of some newer SSL/TLS/HTTPS protocol features (which aren't universally supported), the certificate needs to be served before any regular HTTP traffic is sent across the encrypted tunnel. Which cert do you serve? You can argue that it's probably good practice to not have named based virtual sites on the same IP as SSL sites, or that if you access the SSL site with the wrong hostname it should respond in error, and I think you would be correct. But agreeing on best practices doesn't mean the site is set up wrong, just that it could be set up in a more robust way. It my be set up in a perfectly valid configuration. It's wrong to assume when you can access a site on port 80 that if that same IP address responds to port 443 that it should serve the same site. > The software I utilize checks that, they got it wrong. Return 404 instead. The software you use should be checking that the cert served matches the site requested, and not try to upgrade the connection to HTTPS if it doesn't.
- toast0 12y ago