Home » Update on the problems with the old Blogger blog

Comments

Update on the problems with the old Blogger blog — 9 Comments

  1. Of all the sites I visit, yours is the only one indicated as not secure. Are you aware of this?

  2. About front end problems.

    Seems I was wrong – default settings do not block the redirect. I just created a fresh Firefox profile, not changing any setting, and finally got the redirect behavior you were complaining about. The easiest way around this is to download the HTTPS Everywhere addon (Control+Shift+A to get to addons page in Firefox). Once installed, it will direct everything to the https resource if available.

    The problem of comments not appearing appears to be a separate problem. I spoke too soon yesterday when I said they worked fine. Comments on blog posts before June 28, 2006 seem to be intact. After that, comments are not available on most posts. They may or may not still exist if the pages are accessed through the http protocol, it’s hard to tell since the insecure pages roll over immediately to blogrolling.com.

  3. stu:

    My site here at thenewneo has an “https” designation and all the security stuff is in place. I don’t know why you’re getting a “not secure” message, but that isn’t what I get and it doesn’t seem to be what most other people get.

    If you’re talking about the Blogger blog, the old site, that’s a whole other story.

  4. I also replied on the earlier thread neo… this is a simple suggestion that might fix your problem (without the copying and pasting links, and editing http:// to https:// I mentioned in the earlier thread comment).

    When you go to
    https://www.blogger.com/blogger.g?blogID=0000000#usersettings

    … and change the seven zeros to your blogID ## (you’ll have to login to your Google account too)

    … you might try changing Settings –> Basic –> HTTPS Redirect from “No” to “Yes”.

    Who knows. Might be a simple fix.

    (Mine is set to “no”, but I don’t have the issue… probably due to the vaguely recalled “thing” Google had blogspot users do many, many years ago.)

    Again: you can email me if you need more help.

  5. Of all the sites I visit, yours is the only one indicated as not secure. Are you aware of this?

    Make sure you’re going to https://www.thenewneo.com/ and things should be secure. The site doesn’t re-write your request from http to https automagically. Testing the ssl setup via https://www.ssllabs.com/ssltest/analyze.html gives the site an A, tho the site supports TLS 1.0 and 1.1 which it should not since they’re deprecated, but does not support TLS 1.3.

    Netcraft says you’re running apache. Bonus, they report no know web trackers deployed here. Nice. 🙂

  6. I have the newest versions of Firefox and Chrome, so the problem is not that.

    “Newest” versions of anything, causes loads of problems. There’s a reason why certain pc specialists like to turn off windows automatic updates.

  7. Ymarsakar:

    In this case, though, the problem was also present with the older versions. I can’t remember exactly how long ago I discovered it, but it was before I used the versions I have now.

Leave a Reply

Your email address will not be published. Required fields are marked *

HTML tags allowed in your comment: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>