Page 1 of 1

http:// Images not being visible if hosted off-site unlike https://

Posted: Tue Sep 12, 2023 5:50 pm
by inyanga 1
Obviously not unknown :wall:

Umtali and myself, and some original forumites, have had an issue with their images not being displayed for some time for visitors.

My sig is an example...
http://www.sanparks.org/forums/viewtopic.php?&t=93948


There have been issues with image/filesharing sites (like photobucket, flikr etc) which were previously free
but now force contributors to pay a fee to allow images to be shared on sites like the SanParks forums.

So like U & I we used our own webserver to offer pictures to SanParks websites and others. (interproj.org).
We provided images using http://interproj.org/images/knp/2016/hibus.jpg
rather than https://interproj.org/images/knp/2016/hibus.jpg as we might do now.
I have changed our webserver so it automatically refreshes with https: if an http: request arrives :)

They were setup before SanParks moved to a 'fully secure server' :clap: using https.

We and others (?) were/are impacted as SanParks then enforced secure websites (https:) throughout.

Later on browsers (like Opera, Edge, Firefox) defaulted to disabling insecure content (http:) inside a secure (https:) site:

Whilst it is possible to tweak your personal browser settings to allow 'mixed content (http within an https page, like SanParks) BUT that doesn't allow OTHERS to see your images in line (you have to right click and 'view image').

And also websites, like our own, can tweak incoming http > https that doesn't completely solve the problem.

So a bummer for our Travel tales with thousands of views :wall: :cry: :cry: :cry:

Most interesting posts with images, that are viewed by the public, are Travel Tales. They are viewed via Google links etc.

BUT THEY ARE LOCKED FOR THE CONTRIBUTOR :(

Our Travel tales are locked so we cannot tweak the image links from http:// to https://, and probably cannot afford the time to upload a significant number of replacement images into the SanParks website even if they were unlocked
(the ONLY recommended solution to this problem on the Forum)

Is it possible for the moderators or SanParks Gurus to temporarily, unlock a set of Travel Tales (say for two user id's) :pray: :pray: :pray:

or even run a trivial SQL database command line that converts the string (e.g. http://interproj > https://interproj) within just in those posts?

There was a PHPBB plug-in that would allow such on-the-fly replacemnts for specific destiunation domains, like interproj.org, on the fly but it was discouraged by the PHPBB team :(

Do other forumites have this problem with[ b]personally hosted websites [/b]- not the imaging sharing websites ?

Re: http:// Images not being visible if hosted off-site unlike https://

Posted: Tue Sep 12, 2023 10:41 pm
by Elsa
Is it possible for the moderators or SanParks Gurus to temporarily, unlock a set of Travel Tales (say for two user id's)
Yes, all you have to do is send one of the mods a request to unlock your TR to enable you to replace or repost your images and we will do so with pleasure. :thumbs_up:

Re: http:// Images not being visible if hosted off-site unlike https://

Posted: Wed Sep 13, 2023 8:15 am
by inyanga 1
Elsa wrote: Tue Sep 12, 2023 10:41 pm
Is it possible for the moderators or SanParks Gurus to temporarily, unlock a set of Travel Tales (say for two user id's)
Yes, all you have to do is send one of the mods a request to unlock your TR to enable you to replace or repost your images and we will do so with pleasure. :thumbs_up:
Thanks for the prompt response :gflower:

Re: http:// Images not being visible if hosted off-site unlike https://

Posted: Fri Feb 02, 2024 12:29 pm
by inyanga 1
Hi,

The easiest answer is to ask for your website to 'redirect all http:// to https://' IF it is capable of a secure connection (i.e. with an SSL certificate).

No change to the topics/posts are then necessary... :thumbs_up:

An example of this working is on the SanParks website webserver .. click on the link in my signature which is an http:// and it will be redirected to https:// :whistle: