I don't know how this is possible, but I get

enter image description here

What is happening here? How is it possible? What can be done against that?

  • Not all sites have a certificate. The second link shows the standard untrusted page which is what you get if there's no certificate (and also get if there's something wrong with the certificate). My guess is that only the http link is valid. Commented Feb 9, 2018 at 18:28
  • But it's still a completely different page on the same URL. Previously I thought that HTTP and HTTPS were just different ways to access the same page, but apparently there can be different pages on those. But why? And isn't that a problem for browsers that add http:// or https:// automatically? Commented Feb 9, 2018 at 22:57
  • You can't use https on a site that doesn't have the security layer enabled. (You have to pay yearly for a certificate so small sites that don't generate any income from ads etc tend not to have them.) If I try tex-talk.net I don't get further than the security warning page. Could you add an image of what you see when you try it? Commented Feb 9, 2018 at 23:47
  • Added the picture. Commented Feb 10, 2018 at 9:16
  • 2
    That looks like texfragen.de (which is a secure connection) but notice that it's struck out https so it may be a redirect to a secure link triggered by the invalid https request. (But I'm just guessing.) I think Stefan Kottwitz would be the best person to answer this question (he's the author/host of TeX Talk and, if my limited understanding of German is correct, he's author of the other page as well). Commented Feb 10, 2018 at 11:39
  • 4
    I wrote Stefan a mail with a link to this question. I guess he will have a look at this once a bit of spare time is available.
    – Johannes_B
    Commented Feb 10, 2018 at 14:46
  • 1
    http and https use different port numbers (80 vs 443). There is absolutely nothing stopping someone from running two web servers on the same host, each accepting connections on one of those ports and serving different data. Whether that is wise, is another question; but doing it is trivial. The most common use case is to run a server on port 80 that redirects all requests to https. Commented Feb 15, 2018 at 15:50

1 Answer 1


Update: HTTPS support installed, certificate made with "Let's Encrypt".


Thanks, I will soon get a certificate for the blog and that will fix it.

The blog wasn't https enabled yet, so it happened that it fell back to the next https enabled site on the same server, that's the german FAQ site.

I will update this answer then.


You must log in to answer this question.

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