# "Connection not secure" - normal for SDMB?

**URL:** <https://boards.straightdope.com/t/connection-not-secure-normal-for-sdmb/785078>\
**Category:** About This Message Board\
**Created:** [April 23, 2017, 5:07pm UTC](https://boards.straightdope.com/t/connection-not-secure-normal-for-sdmb/785078 "2017-04-23T17:07:28Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![FloatyGimpy](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/floatygimpy/32/7750_2.png) [@FloatyGimpy](https://boards.straightdope.com/u/FloatyGimpy)\
**Post date:** [April 23, 2017, 5:07pm UTC](https://boards.straightdope.com/t/connection-not-secure-normal-for-sdmb/785078/1 "2017-04-23T17:07:28Z")

</div>

I’ve just noticed that, when I’m on the main page or any of the forum main pages, my connection is secure. Once I click on a thread, I get the “connection not secure” indicator (red lock with line through it).

Is this normal for SDMB and I’ve never noticed it, or is it a new thing or something going wonky on my end?

---

<div class="post-metadata">

**Author:** ![Skywatcher](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/skywatcher/32/254_2.png) [@Skywatcher](https://boards.straightdope.com/u/Skywatcher)\
**Post date:** [April 23, 2017, 5:13pm UTC](https://boards.straightdope.com/t/connection-not-secure-normal-for-sdmb/785078/2 "2017-04-23T17:13:39Z")

</div>

That’s from having https:// before [boards.straightdope.com](http://boards.straightdope.com) or [www.straightdope.com](http://www.straightdope.com). Leave off the https:// if you can, it doesn’t like [straightdope.com](http://straightdope.com).

---

<div class="post-metadata">

**Author:** ![FloatyGimpy](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/floatygimpy/32/7750_2.png) [@FloatyGimpy](https://boards.straightdope.com/u/FloatyGimpy)\
**Post date:** [April 23, 2017, 5:17pm UTC](https://boards.straightdope.com/t/connection-not-secure-normal-for-sdmb/785078/3 "2017-04-23T17:17:09Z")

</div>

> [@Skywatcher](#):
>
> That’s from having https:// before [boards.straightdope.com](http://boards.straightdope.com). Leave off the https:// if you can, it doesn’t like the board.

I don’t think that’s it. At least in my address bar the https… isn’t showing. It just starts [boards.straightdope.com](http://boards.straightdope.com)…

---

<div class="post-metadata">

**Author:** ![Quartz](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/quartz/32/267_2.png) [@Quartz](https://boards.straightdope.com/u/Quartz)\
**Post date:** [April 23, 2017, 5:18pm UTC](https://boards.straightdope.com/t/connection-not-secure-normal-for-sdmb/785078/4 "2017-04-23T17:18:56Z")

</div>

Yup, the board doesn’t use https.

---

<div class="post-metadata">

**Author:** ![Skywatcher](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/skywatcher/32/254_2.png) [@Skywatcher](https://boards.straightdope.com/u/Skywatcher)\
**Post date:** [April 23, 2017, 5:20pm UTC](https://boards.straightdope.com/t/connection-not-secure-normal-for-sdmb/785078/5 "2017-04-23T17:20:33Z")

</div>

> [@FloatyGimpy](#):
>
> I don’t think that’s it. At least in my address bar the https… isn’t showing. It just starts [boards.straightdope.com](http://boards.straightdope.com)…

Whatever browser you’re using is trying to establish a secure connection, that’s what https:// is. You must have it but can’t see it.

---

<div class="post-metadata">

**Author:** ![FloatyGimpy](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/floatygimpy/32/7750_2.png) [@FloatyGimpy](https://boards.straightdope.com/u/FloatyGimpy)\
**Post date:** [April 23, 2017, 5:24pm UTC](https://boards.straightdope.com/t/connection-not-secure-normal-for-sdmb/785078/6 "2017-04-23T17:24:14Z")

</div>

> [@Skywatcher](#):
>
> Whatever browser you’re using is trying to establish a secure connection, that’s what https:// is. You must have it but can’t see it.

I’m using firefox. I readily admit I know extremely little about the workings of the internet and computers in general.

Is it a big deal to have occasionally insecure connections?

---

<div class="post-metadata">

**Author:** ![engineer\_comp\_geek](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/engineer_comp_geek/32/504_2.png) [@engineer\_comp\_geek](https://boards.straightdope.com/u/engineer_comp_geek)\
**Post date:** [April 23, 2017, 5:27pm UTC](https://boards.straightdope.com/t/connection-not-secure-normal-for-sdmb/785078/7 "2017-04-23T17:27:42Z")

</div>

This is a new “feature” in Firefox (and Chome, I think). Basically, the browser is bitching because we have a login box on the page and we’re not using https.

It’s nothing new for the SDMB (we’ve always operated without https), and it’s not that big of a deal, but many of the new browsers are complaining about it.

---

<div class="post-metadata">

**Author:** ![FloatyGimpy](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/floatygimpy/32/7750_2.png) [@FloatyGimpy](https://boards.straightdope.com/u/FloatyGimpy)\
**Post date:** [April 23, 2017, 5:33pm UTC](https://boards.straightdope.com/t/connection-not-secure-normal-for-sdmb/785078/8 "2017-04-23T17:33:05Z")

</div>

> [@engineer\_comp\_geek](#):
>
> This is a new “feature” in Firefox (and Chome, I think). Basically, the browser is bitching because we have a login box on the page and we’re not using https.
> 
> It’s nothing new for the SDMB (we’ve always operated without https), and it’s not that big of a deal, but many of the new browsers are complaining about it.

Ah, OK thank you. At least now I understand what’s happening.

---

<div class="post-metadata">

**Author:** ![aldiboronti](https://avatars.discourse-cdn.com/v4/letter/a/9fc348/32.png) [@aldiboronti](https://boards.straightdope.com/u/aldiboronti)\
**Post date:** [April 23, 2017, 6:20pm UTC](https://boards.straightdope.com/t/connection-not-secure-normal-for-sdmb/785078/9 "2017-04-23T18:20:46Z")

</div>

Browsers are adding new bells and whistles as they try to keep up with Chrome in the constant struggle to attract new users or keep the old. (It’s a war that Chrome has already won with 90% of the market.) Many of these so-called security features are unnecessary (at least at present) and some are a bloody nuisance.

---

<div class="post-metadata">

**Author:** ![BigT](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/bigt/32/12044_2.png) [@BigT](https://boards.straightdope.com/u/BigT)\
**Post date:** [April 23, 2017, 7:50pm UTC](https://boards.straightdope.com/t/connection-not-secure-normal-for-sdmb/785078/10 "2017-04-23T19:50:42Z")

</div>

If it annoys you too much, you can turn it off. I did, since it kept covering up dialogs I needed to use.

Copying the directions straight from a Google search:

[ol]  
[li]Open Firefox.[/li][li] In the address bar type the following command:[/li][li] about:config.[/li][li] Click on the “I’ll be careful, I promise…” button.[/li][li] In the Filter field type: security.warn\_entering\_secure.[/li][li] Double-click on this entry and set its value to False.[/li][li] Close the about:config window and restart Firefox.[/li][/ol]

---

<div class="post-metadata">

**Author:** ![FloatyGimpy](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/floatygimpy/32/7750_2.png) [@FloatyGimpy](https://boards.straightdope.com/u/FloatyGimpy)\
**Post date:** [April 23, 2017, 8:13pm UTC](https://boards.straightdope.com/t/connection-not-secure-normal-for-sdmb/785078/11 "2017-04-23T20:13:46Z")

</div>

> [@BigT](#):
>
> If it annoys you too much, you can turn it off. I did, since it kept covering up dialogs I needed to use.
> 
> Copying the directions straight from a Google search:
> 
> [ol]  
> [li]Open Firefox.[/li][li] In the address bar type the following command:[/li][li] about:config.[/li][li] Click on the “I’ll be careful, I promise…” button.[/li][li] In the Filter field type: security.warn\_entering\_secure.[/li][li] Double-click on this entry and set its value to False.[/li][li] Close the about:config window and restart Firefox.[/li][/ol]

Thank you!
