[img] problem

Sir Osis of Liver · January 10, 2024, 12:40:33 PM

One of my guys is having a problem viewing images that are posted in img tags. It only affects him (admin) and some members. The images are not displayed, and he can't link to them directly. He's tried several browsers on different devices. I can see the images in the posts and with direct links. He posted a couple on my support forum, he can't see them but I can. Oddly, Crocweb support can't see them either. The images in the original post are posted like this:

[img]http://www.carsntrucks4you.de/images/crackerbox/GMC Crackerbox_1.jpg[/img]

Can you see it here?

Support tells me this:

The issue is caused by the SMF forum using https which causes the images to also be accessed using https protocol but those image URLs do not have SSL installed. This is not an issue with your SMF forum or the server. Please check the attached screenshot.

Screenshot attached.

Only unusual thing I've noticed is if I open image in new tab, url is displayed like this:

http://www.carsntrucks4you.de/images/crackerbox/GMC Crackerbox_1.jpg

But when I copy it from address bar it pastes like this:

http://www.carsntrucks4you.de/images/crackerbox/GMC%Crackerbox_1.jpg

I can view it either way.

Version Information:
Forum version: SMF 2.0.19 (more detailed)
Current SMF version: SMF 2.0.19
GD version: 2.3.3
Database Server: MariaDB
MySQL version: 10.6.15-MariaDB-cll-lve
PHP: 8.0.30
Server version: LiteSpeed

Aleksi "Lex" Kilpinen · January 10, 2024, 12:44:35 PM

A space is not a valid character in an url.
It should be http://www.carsntrucks4you.de/images/Crackerbox/GMC%20Crackerbox_1.jpg (Or preferably, it shouldn't have the space at all in the filename)

Also, you basically can not view HTTP content in a HTTPS webpage. Here, the image is proxied and presented as HTTPS.

Sir Osis of Liver · January 10, 2024, 12:48:46 PM

But it works for me as posted with the space. I've posted it on my forum with the % replacing space, waiting for reply if he can see it.

How is it proxied?

Aleksi "Lex" Kilpinen · January 10, 2024, 12:49:58 PM

I just added this to my earlier post while you were replying.

Quote from: Aleksi "Lex" Kilpinen on January 10, 2024, 12:44:35 PMAlso, you basically can not view HTTP content in a HTTPS webpage. Here, the image is proxied and presented as HTTPS.

2.1 has the image proxy built in, there are mods for this as well.
https://custom.simplemachines.org/index.php?mod=4173

Sir Osis of Liver · January 10, 2024, 12:55:27 PM

2.0 has an image proxy setting, when I enable it I can no longer see the images.

Aleksi "Lex" Kilpinen · January 10, 2024, 12:59:07 PM

Honestly can't remember if 2.0 had the same functionality already, but if turning it on breaks the images then something might not be working right.

shawnb61 · January 10, 2024, 01:17:03 PM

The 2.0 proxy was brought up to date with the 2.1 proxy fixes, etc., at one point. The proxy should be good if you're on 2.0.19.

What I see happening with that image, with the proxy OFF in 2.0, is a browser security warning. Some browsers/settings will hide that image and note why in the console log. That would explain why some folks can't see it with the proxy off. That is expected behavior - with each release, all browsers are getting increasingly strict about mixed content. To fix, they either need to lower their browser security settings, OR, add an exception for that site in their browser.

With the proxy ON in 2.0, I see the pic served up properly, and no browser warning, as expected. I'd double-check that you have the URL & spaces straightened out.

Sir Osis of Liver · January 10, 2024, 08:38:05 PM

Can you see the image here? Proxy is disabled, image is posted as [img]http://www.carsntrucks4you.de/images/crackerbox/GMC Crackerbox_1.jpg[/img]. I see it in FF 115, no security warning. All security and privacy settings are maxed, Ghostery has no problem with it. It displays correctly with space in file name in forum and with direct link.

shawnb61 · January 10, 2024, 11:12:53 PM

Yes, lots of security (and other) warnings & errors.
You cannot view this attachment.

The space isn't the problem - the insecure link is.

Although technically incorrect, 2.0 supported spaces in filenames under certain circumstances like this. After discussion, we added that to 2.1 also - mainly because folks had images disappear on them after migration. So now 2.1 will allow a space in there as well.

shawnb61 · January 10, 2024, 11:54:57 PM

FYI, on Chrome & Edge, default install settings, that image doesn't appear.

Sir Osis of Liver · January 11, 2024, 03:14:10 PM

Any way to fix this for all users? If image proxy is enabled, image doesn't display.

Sir Osis of Liver · January 11, 2024, 03:41:06 PM

Where did you get FF 121? My browser is showing up to date at 115.6, no updates available.

Aleksi "Lex" Kilpinen · January 11, 2024, 03:43:48 PM

121.0 came in december, there's already a 121.0.1 released this month too.
You must be running Firefox Extended Support Release (ESR), that's stuck on 115.6 for now.

Sir Osis of Liver · January 11, 2024, 03:45:46 PM

Firefox is no longer supported on Windows 8.1 and below.

Crap.

Sesquipedalian · January 11, 2024, 03:46:41 PM

Quote from: Sir Osis of Liver on January 11, 2024, 03:14:10 PMAny way to fix this for all users? If image proxy is enabled, image doesn't display.

The tests by everyone here demonstrate the opposite. (That's the whole point of the image proxy, after all.)

This means that on the forum where the image does not appear when the image proxy is enabled, there is most likely something going wrong with the image proxy on that particular server. Specifically, if the proxy script is unable save a local copy of the image to the cache, or unable to retrieve that local copy from the cache, then it will be unable to serve the image when requested.

I suggest that you start by checking file permissions and disk space in the ./cache/images directory (replacing ./cache with the correct path to the forum's cache directory, of course).

Sir Osis of Liver · January 11, 2024, 04:00:19 PM

/cache/images is 755, plenty of disk space. When I enable proxy image disappears, no file in cache. Same with caching enabled or disabled. Reposted several times with different cache settings, same thing.

Arantor · January 11, 2024, 04:06:27 PM

Quote from: Sir Osis of Liver on January 11, 2024, 03:45:46 PMFirefox is no longer supported on Windows 8.1 and below.

Crap.

I should add that we had the discussion, what, a year ago about the fact that Win8.1 was going out of support, that you wouldn't be getting the extended support (because that's reserved for the expensive customers) and that as a consequence, software was going to stop supporting it anyway because it's not worth it for their developers.

Windows 10 is 9 years old and goes out of regular support next year so Win8.1 is... getting on a bit.

Sir Osis of Liver · January 11, 2024, 04:22:12 PM

There are several reasons I haven't upgraded from 8.1 -

Win 10 and 11 are expensive.
Downloads are huge and MS servers are very slow.
Win 10 and 11 are expensive.
I like 8.1, it looks/works just like XP in Classic Shell. I liked XP.
Win 10 and 11 are expensive.
Classic Shell is not available for Win 10/11.
Win 10 and 11 are expensive.
There's a good chance upgrade will crash my computer and make it a brick.

Did I mention Win 10 and 11 are expensive?

Illori · January 11, 2024, 04:37:29 PM

i bet if you tried you could use the same key you have for windows 8.1 and use it for windows 10 or 11.... i know mine for windows 7 worked fine for windows 10, so windows 10 cost me 0 extra dollars.

Sir Osis of Liver · January 11, 2024, 04:41:37 PM

Wouldn't have any idea where to find the key, and I believe MS ended free upgrades quite some time ago. I had a MS support account, which might still entitle me to free upgrade, but they've locked the account.

But that's really beside the point. I'm trying to fix this image problem for all users, I can see the posted pics fine.

News:

[img] problem