Broken Image links

Am I alone in not being able to see any images?

I'm geting a grey line with a blue '?'

If I right click and open image in new tab I get "Page not available".

Problem with the forum or with me?

I'm having the same problem, using Chrome on windows.

Images work on my HTC though.

Perhaps this should be in the mods thread or bugs & fixes.

Yep, me too. Works in Firefox though.

had images first thing this morning now not visible

this has just started for me too: Google Chrome Version 21.0.1180.75 m

example when images DO work: http://www.lfgss.com/thread91204.html
(seems to be when images are uploaded to LFGSS only)

example when images DO NOT work: http://www.lfgss.com/thread91194.html
[INDENT][INDENT][/INDENT][/INDENT]

when i hover over the image i get a functioning URL as the 'ALT' text that can be added to an HTML string. when i right-click and copy URL (instead of getting http://farm9.staticflickr.com/8421/7727779064_bd3f6be87b_c.jpg) i get http://www.lfgss.com/://sslcache.se/c90c5d01094be4b394347677f4fc9597974b2957/687474703a2f2f6661726d392e737461746963666c69636b722e636f6d2f383432312f373732373737393036345f626433663662653837625f632e6a7067

inspecting the element shows the problem, the SRC value is for sslchache.se (website gives message "Proxy for images served on LFGSS, ask Velocio if in doubt."):

[INDENT][INDENT][/INDENT][/INDENT]

now working fine

I'm on Safari. (I know, using the stock browser is so passe but there you go)

Most images seem to be working again but seen a few examples of broken ones.

Happening on all images for me on Chrome and IE9, still.

I'm getting no images with Chrome or the stock browser on Galaxy S3.

No images here, Firefox on Windows 7

http://cl.ly/image/3L0q240D2F1U

yeap nothing here chrome, osx lion

What happens to images depends on how you access LFGSS.

If you access via http://

Then you just get the images from the remote servers... i.e. Flickr, Facebook, Imgur or wherever the image is hosted.

In which case, I cannot help... they're nothing to do with me.

If you access LFGSS via https://

Then what happens depends on where the image comes from.

If it's from LFGSS, I just serve the image.
If it's from Facebook, Flickr, etc... then you get the image from them over their https:// connection.

If it's from any http:// source that doesn't have a https:// source, then I do get involved and do something strange. I proxy them... which means I have my server go get the copy (over http://), and then my servers sends you the copy over https://

This is to ensure that you get a green lock in the top of the screen and no errors about mixed content.

The issues that can occur with my forwarding images are:
1) I'm using a service called Heroku, and that might go down.
2) Heroku uses Amazon S3 cloud services, and that might go down.
3) In front of both of those is a service called Amazon Cloud Front, and that might go down.

Such occurrences should be rare, and will only affect http:// images requested over https:// and proxied through the https://sslcache.se/ domain.

All make sense?

In which case... I don't know why images suddenly stopped in the examples given.

For example, in Jambons post ( https://www.lfgss.com/thread91194.html ) are these image links:
http://farm9.staticflickr.com/8421/7727779064_bd3f6be87b_c.jpg
http://farm9.staticflickr.com/8287/7727781106_fafd939d48_c.jpg
http://farm9.staticflickr.com/8288/7727782798_0794046612_c.jpg
http://img705.imageshack.us/img705/9503/systemsix2.jpg

Notice that they're all http:// links, so when you access LFGSS via https:// you would normally get a mixed content warning and won't see the images.

To ensure that you see the images, when you access LFGSS over https:// the image links are changed to:
https://farm9.staticflickr.com/8421/7727779064_bd3f6be87b_c.jpg
https://farm9.staticflickr.com/8287/7727781106_fafd939d48_c.jpg
https://farm9.staticflickr.com/8288/7727782798_0794046612_c.jpg
https://sslcache.se/a5bd740f0d18df8ab499166494da34e78c1ac1e0/687474703a2f2f696d673730352e696d616765736861636b2e75732f696d673730352f393530332f73797374656d736978322e6a7067

Notice that now they're all https:// links.

The first 3 are all on Flickr, and Flickr offer https:// so you're now just getting the secure version of the image. But if the image is broken... it's 100% Flickr's doing.

The last image is ImageShack.

The URL is:
http://img705.imageshack.us/img705/9503/systemsix2.jpg

But no image exists at:
https://img705.imageshack.us/img705/9503/systemsix2.jpg

So I will have to proxy it:
https://sslcache.se/a5bd740f0d18df8ab499166494da34e78c1ac1e0/687474703a2f2f696d673730352e696d616765736861636b2e75732f696d673730352f393530332f73797374656d736978322e6a7067

The sslcache URL is made up of two bits:
https://sslcache.se/${secretKey}/${imageUrl}

The ${imageUrl} is simply http://img705.imageshack.us/img705/9503/systemsix2.jpg hex encoded (so I can pass it around safely).

And the ${secretKey} is a HMAC based on a shared secret and hash with the image URL. It's only there to prevent non-LFGSS sites from using sslcache to proxy images.

What sslcache does is:
1) Check the imageUrl is good (validated by the secretKey)
2) Fetch the image from imageURL
3) Serve the image

That's literally it, there's no logic to speak of... I just fetch the image and serve it.

Again, I only do this for http:// images that have no https:// source when you access via LFGSS over https://

And I can't explain the broken images above, as 90% of them in the examples shown come from remote servers and I've not touched the links at all.

So... I dunno what's happening there. Temporary glitch in the wider matrix?

Velocio, even on https the images are still served to me (imageshack included) so i think it could have been a temporary thing.

Mine is fine now too.

I thought so.

I just wanted to make sure people know what I'm doing, and when I'm doing it.

That way when stuff breaks you know where to look.

i.e.: If images from Flickr aren't loading... open them in a new tab and hit refresh to try and see what the issue it.