Changing over to https everywhere

[CabinetGuy]

I am looking to go https for my entire website but over the years i have identified image files with a standard http:// address. Now I want to identify them with https:
Would this statement do the job in phpmyadmin? :

UPDATE products_description SET products_description=replace(products_description, 'http://website.com', 'https://website.com')

or is there a better way to go https throughout the site?

tia

[stevesh]

May we ask why you want to secure the whole site? That may cause slow page loads and other issues with no discernible advantage I'm aware of.

[CabinetGuy]

Here is the headline...

https://blog.digicert.com/google-giv...ranking-boost/

I rec'd notice about a week ago that google will be evaluating sites with https for increased rankings...

thx

[gilby]

Here is the headline...

https://blog.digicert.com/google-giv...ranking-boost/

I rec'd notice about a week ago that google will be evaluating sites with https for increased rankings...

thx

Hmmm I wonder if that's been taken out of context by that site with a vested interest?
Just asking?
Maybe I'm too cynical?

[CabinetGuy]

granted, not all folks are for it...but doggone...google rankings being what they are...and I already have a private ssl cert....

Here is another opinion about the Google https Everywhere Initiative:

http://www.2rosenthals.net/wordpress...t-so-fast-994/

It was my SEO company that notified me....

[CabinetGuy]

here is the Google announcement:

http://bit.ly/sslseo

Keith

[stevesh]

Huh. It was Google's insistence on using https on its own site that led me to switch to Bing for search (well, that and the inability to turn off auto-complete).

Sorry, I'm not SQLer enough to comment on your proposed statement, but there are many here who are. If the reply turns out to come from RodG we may hear his comments on the 'security theater' aspects of SSL, which are pretty much the same as mine.

[CabinetGuy]

thx....we'll see...

I don't see a problem with the sql statement...I just wanted to verify...with someone much more adept than me.

thx again.

[mc12345678]

I've found that provided the server being reached serves the item(s) via https that provided page is served http or https, then the prefix http: or https: need not be included and the associated image/link will happen in the form of the served page. So if the above SQL format is considered correct, then the replacement would be something like:

UPDATE products_description SET products_description=replace(products_description, 'http://website.com', '//website.com')


The browser used will apply the appropriate method. Now, this does not work if the address identified above is used in an href type tag, but does work for data types like images where say src="//server/path/image".

But, there is also the aspect that, why is the server being listed/identified if the image(s) are locally stored, and if they are not locally stored, why not? Wouldn't simply a relative reference be appropriate for the locally stored image(s)?

[CabinetGuy]

over the years, I have learned a few things...in the past, I thought I had to include the http: in the image location path names.

It never made any difference until now that some of them had the http:, now it does. So, I think the ammended sql string is appropriate to eliminate the http: from the local addresses.... So, now I would have to make sure that any href tags are not included in the process, only image files...

thanks