Web Weather > Weather Web Site Help

SSL Certificate and secure site

(1/3) > >>

PaulMy:
Is it as easy as buying the SSL certificate and then editing .htaccess as GoDaddy says?   https://ca.godaddy.com/help/redirect-http-to-https-automatically-8828??v=1

Paul

wvdkuil:

--- Quote from: PaulMy on March 08, 2018, 10:38:30 AM ---Is it as easy as buying the SSL certificate and then editing .htaccess as GoDaddy says?   https://ca.godaddy.com/help/redirect-http-to-https-automatically-8828??v=1

Paul

--- End quote ---
No, you have to check all pages if they contain links to http files, javascript for graphs and the like.
Normal http images will only give the "unsecure' warnings, but http javascripts and iframes will  only show white areas on the pages.

Step 1: have a https certificate
Step 2: all visitors  still go to the http site
Step 3; you check every part of all your sites it there is an error (in chrome inspect => console tab) and check if you can find https sources
When all is OK => switch to htpps with the  htaccess but only AFTER you made a solution for thos pages you still want to show but which will not work under https.

Yes. it is doable, but take far more work then the sellers of https talk about,

Wim

PaulMy:
Thanks Wim.
GoDaddy had called to warn me of the upcoming issues on unsecured sites.  I can get the Standard UCC SSL for up to 5 domain sites.   

I understand that I can add my sites one at a time as SSL secured so maybe the best way is to buy and start with adding one domain at a time.  I have 3 domains for not-for-profit organizations that have very simple websites so not too difficult to experiment with these first before I go to the weather sites.

These are all under my komokaweather.com hosting but in talking to GoDaddy hosting is not affected as unsecured, just the domains.  I presume that once I add a domain to the SSL certificate then the green padlock will appear on that domain's pages.


--- Quote ---Step 3; you check every part of all your sites it there is an error (in chrome inspect => console tab) and check if you can find https sources
--- End quote ---
I seldom use Chrome so not familiar with the various functions (not familiar with them in Firefox either :oops: ).  I presume you mean that when a site is open in Chrome then press [F12], then [Console]. and with that I get clean results in the 3 simple domains and komokaweather.com. 
In komokaweather.ca (Saratoga template) I get one 404 (not found) which is at weatheroffice.ec.ca and I presume that is out of my control.

Or is there another function way to check on the https sources?

Again thanks and appreciate the guidance.

Paul

wvdkuil:

--- Quote from: PaulMy on March 08, 2018, 01:45:50 PM ---Thanks Wim.
GoDaddy had called to warn me of the upcoming issues on unsecured sites.  I can get the Standard UCC SSL for up to 5 domain sites.   

I understand that I can add my sites one at a time as SSL secured so maybe the best way is to buy and start with adding one domain at a time.  I have 3 domains for not-for-profit organizations that have very simple websites so not too difficult to experiment with these first before I go to the weather sites.

These are all under my komokaweather.com hosting but in talking to GoDaddy hosting is not affected as unsecured, just the domains.  I presume that once I add a domain to the SSL certificate then the green padlock will appear on that domain's pages.


--- Quote ---Step 3; you check every part of all your sites it there is an error (in chrome inspect => console tab) and check if you can find https sources
--- End quote ---
I seldom use Chrome so not familiar with the various functions (not familiar with them in Firefox either :oops: ).  I presume you mean that when a site is open in Chrome then press [F12], then [Console]. and with that I get clean results in the 3 simple domains and komokaweather.com. 
In komokaweather.ca (Saratoga template) I get one 404 (not found) which is at weatheroffice.ec.ca and I presume that is out of my control.

Or is there another function way to check on the https sources?

Again thanks and appreciate the guidance.

Paul

--- End quote ---
When you run your current site now, you see the errors using http.
When you have a certificate you should add that site, but without forcing the use of HTTPS, so without htaccess redirect.
You then can test the site by accessing it yourself with https:// and  see if there are errors.
Example http://www.komokaweather.com/ at that site there are 90 http:// links, most of them probably links to other websites which will open in a new tab.  Those external websites do their own redirecting, nothing to bother with now.

But some of them must be changed not to loose functionality on your own pages, examples: http://c.statcounter.com   http://s48.sitemeter.com http://localtimes.info/  http://www.komokaweather.com/weather/wu/image_wu.jpg http://weather.gc.ca/data/warningmap/son_e.png

So that will take some time,  and checking if these images and javascripts are available under https.

Succes, Wim

PaulMy:
OK, thanks Wim I think I understand better now.

Regasrds,
Paul

Navigation

[0] Message Index

[#] Next page