Hi guys,
What am I doing wrong? My cell phone uses Chrome and the images do not appear. My laptop with Vivaldi and FF works fine, but not with Chrome or Edge, or Opera
So i'm having different responses (the images do not appear in Chrome but do appear in FF) here's the posting code:

There is every possibility that your photo app or browser is corrupted. You will need to clear all cookies and the cache.
Reboot your device afterwards.

Greg.

I cleared the cache and cookies but the images from the code above do not show up.
posted code:
[img]http://www.pbpix.com/BELKNAP-1.GIF[/img]

The only difference is that the posted code has the "[img]"---"[/img]" in the line

But if I enter this string directly in my address window of Chrome the image shows up.
http://www.pbpix.com/BELKNAP-1.GIF

What graphics programs do you have?
click on, windows Settings, then Default Apps by file Type, They will show which graphics extensions are checked and can be changed.
and the list of Windows Picture, Windows Media Player or Power Media Player, Paint, Adobe, etc.
and while there you can designate which app you can apply.

Or browse for something like this
https://www.startpage.com/sp/search

Edit: I digress, I forgot you said Cell phone. But since I won't use a cell phone (privacy). I would guess the same would apply?

I'm not with you. The images are showing here on my Mac.

A space is assigned number 32, which is 20 in hexadecimal. When you see “%20,� it represents a space in an encoded URL, for example, http://www.example.com/products%20and%20services.html.

The images don't show inline here but do show with "show image in new tab." in Chrome.

The links are non-secure (HTTP: vs HTTPS:), most browsers will not show insecure content on a secure page. Tried as https:// and the site does not provide a secure protocol.

I have the same problem viewing those image files here using latest Chrome version under Windows 7 or 10.
The same images display fine under ie 11 or edge.
I've had that problem on ARF using Chrome for some time now, and haven't figured out what specific setting or permission is necessary to correct the issue.
It seems to happen most often when viewing images in older threads.

This is the cause of the problem. Different browsers handle non-secure content differently. antiqueradios uses the secure HTTPS protocol and your site does not.

How can I support it on my site?
And why does it only happen when the AR image code is added ie:"[img]"

How is your site hosted? If it is done by a hosting company then they should be able configure their server software to support HTTPS.
If it is done on your own computer then you have to get a certificate and configure your server to use it.
As for the problem only occurring when using img, img says to display the picture within a page from antiqueradios. and that is where you have insecure content within a secure page.

It's because this antique radio forum became a secure site one or two years back.
(by adding the S to http)

Causing your problem of mixed content. (insecure image - - secure site)

adding https to my http site
https://www.google.com/search?q=adding+ ... 8&oe=utf-8

So is there any way to instruct Chrome to display insecure content within the secure page on ARF? Is there a rule that can be implemented just for this site?
I'd really like to be able to look at the many images on older posts that won't display without having to open another browser.

ARF is hosted on goDaddy servers or got there domain name though.

Ask your hosting site. On mine, it was by adding an SSL certificate and setting up its home directory (to the same directory as my home page as regular HTTP.)

[img] will put the image inline (within a secure page). Just a link would open a separate page that can be insecure. Chrome will not by default allow insecure content within a secure page.

But.... so you are saying it's a browser issue?
because Chrome doesn't allow it but FF does allow it ?

Yes, it's a browser issuer. It is done for security, disallowing insecure links on a secure page. Otherwise, it would be much easy for bad actors to disguise malicious content with what appears to be a secure webpage.

Yes, most all sites are now secured via SSL (HTTPS). For about 10 years, browsers have warned or not allowed unsecured web sites. For a while, Chrome would not even give me an option to connect to a local unsecured server. They now have an option to "proceed at your own risk."

Surprises me that FF allows it but they do some checks if the content is safe.

Typical, Edge is based on the same code as Chrome but Microsoft has reduced the security settings. One of the reasons I never use a MS browser except to download a better one.

Google was a big proponent of the push to all HTTPS secure internet and they own Chrome, hence the implementation of the policy.

Thanks but...Been there, done that. Problem persists.