Re: Feature request: Image Proxy
Reply #3 –
I knew I wrote something!! xD
I wasn't able to find it as well... LOL
Re: Feature request: Image Proxy
Reply #4 –
Time for a bump!
I think we finally need to pull this into the 1.1 core (and possibly for 1.0.10) as the Chrome mandate is just about here. As I understand it Chrome will begin to flag screens with password inputs, on non-https servers, as insecure.
Thats not really an ElkArte issue but a server / site issue. However once someone enables https, they will need the image proxy to still allow links to http sites from your https site, something ElkArte should support out of the box.
Re: Feature request: Image Proxy
Reply #7 –
If you get that in a branch somewhere that would be cool. I'm looking to beef up the proxy a bit so have been working on that.
Re: Feature request: Image Proxy
Reply #11 –
I've added the basics for retry on fail for images that don't fetch properly. It will try 10 times to get the image on a ^4 based timer curve. Nothing fancy but basically waits longer each time it fails until it trys again. On failure it just shows the default mime thumbnail.
To do the above I added a new table to track the image / time / failures to the db, so 1.1 will need a new table for this. This same table will be used for prune operations so "old" images (ones that have not been accessed in X time) can be removed from the cache. Thats the next bit to do.
Re: Feature request: Image Proxy
Reply #12 –
I don't think https image shown in http site is a problem, however, the vice versa is i.e. http image in https site.