I get so little following and those that do, are return. Depends on how exciting the weather is. meh…
Maybe later if I decide I want to keep the site running. I am 71, that is getting up there.
Fully agree. Been with my host for ~15 years - they want to charge for a cert. Not gonna happen. Even if for some reason I was ‘forced’ into SSL I would move to a new host first. Will be 76 in May (maybe) - probably dead by then, anyway…
Is it only Google requiring this?
Firefox browser is also heading in the same direction as Chrome, but not so aggressively.
Quote from: jgillett on [b]Today[/b] at 06:49:11 AM
Fully agree. Been with my host for ~15 years - they want to charge for a cert. Not gonna happen. Even if for some reason I was ‘forced’ into SSL I would move to a new host first. Will be 76 in May (maybe) - probably dead by then, anyway…
Wow, this forum has a lot of old f#$ts in it! :lol: I just turned 78 myself…
Anyway, I use 1and1.com for all of my hosting and domain handling. They provide FREE SSL certificates. I am in the process of enabling SSL on all of the websites I manage.
just sent another note to my district admin. Don’t want to get caught this summer when many are on vacation.
So is it a certificate? or is it going from http:// to https:// or both
Chicken and egg 
You can’t go https:// without a certificate.
Being close to the 7x’s I was feeling pretty old this morning until I caught up with this thread, now I realize I’m just a youngster 
I used to think I was in the “geezer” category, but realize now I am in the “Old Fart” realm. Just remember, “Old age and treachery always overcome youth and skill.”
We might consider renaming this thread to… Google to Condemn insecure Geritol websites ?
I went ahead and going to do comodo[s positve ssl. 111 for a year and then throw my hands in the air and scream
However, I did take prune juice, miralax and a Linzess so I better do that in comfort of the bathroom.
What Hostmoster said is that they would do the deed, then put in a redirect for those who do the http and i should be good. the problem is something is wrong with my pay thing. it generates an error that they are tracking down.
So later…
@ALL
That is a BAD advice form the provider. Never set that redirect until your website is fully httpS tested with all possible pages and with all extras such as weather alarms a.s.o.
Your customised template is huge and normally it will take a user with basic php knowledge about two weeks to check and adapt everything.
A correct procedure would be that all users
use the current site http://desmoinesweather.org/weather28/ and can visit all pages without interruptions or error messages.
You, as the tester
[ul][li]You will add https in front and will be the only one knowing that https://desmoinesweather.org/weather28/ exists[/li]
[li]You will have two browser windows open to the same page, one with http and one with https[/li]
[li]You will then check wat is NOT displayed on the https one and if the “unsafe” or “safe” icon is displayed in the browser address field
Some 30% of the pages need some to a lot of work.[/li]
[li]Do inspect => console and you will see the error messages, mostly http images or http scripts which were denied loading into a https page.
You will find swiftly if the http link can be substituted with a https one, more then half of the pages can modified that way.
[/li][/ul]
Otherwise remove the page from the menu and put it on a TODO list.
If your sites runs acceptable under https, THEN and ONLY THEN you can afford yourself a redirect. But even then i would not use a redirect you can not modify yourself.
All users will follow the providers https redirect, no way to exclude one or more pages which do not run under https yet or never will.
I prefer the redirect in your own root .htaccess such as the example below, which will do the redirect, but not for pages with a special name or token
Options +FollowSymLinks
RewriteEngine On
RewriteCond %{HTTPS} on
RewriteCond %{QUERY_STRING} htp
RewriteRule ^.*$ http://%{HTTP_HOST}%{REQUEST_URI} [R=301,L]
RewriteCond %{HTTPS} off
RewriteCond %{QUERY_STRING} !htp
RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [R=301,L]
Wim
This old f%&t bit I’m definitely in the f%$t category but not quite in the old bit yet (61). 
teal.
Or maybe the best solution would be for me or others, to continue on as we are currently doing and not give a rat’s rear what google is going to do. from my analytics it seems that the same users come to my site and new users not so much. So what if Google lists my site as unsafe, I would assume that if I post something up on the maintenence section what Davis is going to do, it might solve this whole thing.
This was the response. At least they are aware.
[See this web page for more specifics on the change:So the page will still be accessible on http, but there will be a note next to the URL that says “Not Secure”.
Your current web site domain is weather.rms.rdale.org. It appears we are not currently hosting it as an https web site.
With the wildcard certificate that we currently have, and most other wildcard certificates, we can use it with *.rdale.org, but not ..rdale.org, so if you want to use the web site with https, we would either need to purchase a certificate specifically for that domain or change your domain to something like weather-rms.rdale.org or rms-weather.rdale.org.
It is my understanding that they will list your site and mine as not secure. I have a small cadre of people who view my site. Already I have posted that google is going to do this and my site is safe.
I was going to go with Comodo’s Positive SSL for 5 bucks a month but it was not advised to go SSL because on my templates that I use from Leuven, there is a question will the various links that are identified to being http and referring back to my site might not operate right.
Considering cost, of the certificate plus the static IP which seems to be necessary as well, it isn’t worth the added expense for someone like me at this time. My best option is to be vetted by other search engines.
It sounds like they are willing to move my site to another certificate and make a minor rename. Then add a forwarding to my old site. I should not have to do much recoding since anything for my site is in my files.
Whew. May get done in the next month.
When I was teaching, we had our own IT people and they would do things like that. However now it is up to me. I think what I am going to do is take my chances. I have Leuven templates and Wim implied that changing over to https, would cause problems for the templates. So I am going to wait and see what he comes up with. Hostmonster said that they could, for a fee, add the certificate and a static ip address, then after everything was in place, put a redirect in for me so if someone went to http, they would be sent to the https site.
So I am waiting.