How are the images posted? BBcode (default or custom), a plain link, an extension?lemACD wrote: βWed Mar 03, 2021 5:01 pm Since upgrading to 3.3.3 I've found that some images don't appear.
If I right-click the image and click 'open image in new tab' then the pictures are there so nothing obviously wrong and they used to work.
At first I thought that the ones that aren't showing had http: addresses and the ones that are OK were https: but I've just found one http: picture that's working fine so that doesn't seem to be the pattern.
Any suggestions please?
Sure.warmweer wrote: βWed Mar 03, 2021 5:16 pmHow are the images posted? BBcode (default or custom), a plain link, an extension?lemACD wrote: βWed Mar 03, 2021 5:01 pm Since upgrading to 3.3.3 I've found that some images don't appear.
If I right-click the image and click 'open image in new tab' then the pictures are there so nothing obviously wrong and they used to work.
At first I thought that the ones that aren't showing had http: addresses and the ones that are OK were https: but I've just found one http: picture that's working fine so that doesn't seem to be the pattern.
Any suggestions please?
A link to your site with an example post (e.g. the http one that's OK, and one that's not OK) could help (or better even the Support Request Template providing information about your site specifics.
Code: Select all
[img]http://www.ukrockfestivals.com/henge-84-dude-van.jpg[/img]
[img]http://www.ukrockfestivals.com/convoy-steve-van-400.jpg[/img]
[img]http://www.andyworthington.co.uk/images/stonehenge1984.jpg[/img]
Purge forum cache and browser cache and then look at that post again.
The issue described happens for me, for what it's worth:
I'm also accessing it via HTTPs but ... I was using FF ad didn't think about other browsers : now tested with the others
Concerning FF, thanks to EA117 I found the "culprit" quickly.
For what it's worth, I think that's different than the mixed-content control, which FireFox also provides. HTTPS-only mode would upgrade even your connection to a single page, if that page were available on HTTPS and HTTP. Mixed context control is, of course, when mixed sources exist. HTTP-only mode might attempt to upgrade those to HTTPS, but whether or not it can depends on the source, not on FireFox. Mixed-content control decides "what to do when the content is coming from HTTP", whether HTTP-only attempted to upgrade the connection or not.HTTPS-Only Mode
I think part of the "why now" is that the browsers themselves are evolving, and both providing & reacting to things differently in order to increase their default security posture as compared to previous versions.