Jump to content

Community

Whitelist image cache


Recommended Posts

Or you may call it a blacklist, depending on your perspective.

Thing is (even though I hate it), lots of our member have a ticker-image running in their footer. But these are not updated anymore due to the image-cache (which works brilliant besides this issue).
what would help is a option for a small list of  "whitelisted domains". Images from those domains will not be cached. Problem solved, everybody happy :)

Sounds like a plan?

Edited by Sledge FTB
Clarification
Link to post
Share on other sites

Next question is, how do we get some attention from a developer?

Or are their other possibilities?
It is quite easy to let a cronjob do the dirty work and delete any cached image from domain whatever.com. But I have a feeling that that will at least break the images in their relative post, but it even might screw up the complete cache server.

 

Another idea ... instead of a white/black-list, an attribute as image option as a kind of (cache) opt-out, would do as well. 

Edited by Sledge FTB
Link to post
Share on other sites
  • 1 month later...
  • 1 year later...

A year has passed and it still seems weird that we're quite alone on this one.

A small exclusion list, on which you can add domains to not be cached by the imageproxy would be great. Not only to use tickers, but plenty other sites share information through images and update those images over time.

Link to post
Share on other sites
On 6/27/2017 at 3:04 AM, Sledge FTB said:

Next question is, how do we get some attention from a developer?

You got it by posting in the feedback topic. If there is no traction to your request it might never be implemented though. 

Personally, I neither have “ticker images” images on my sites nor do I use any site that has those. And the proxy cache feature (which I assume you are referring to) already has an option to set a cache time. So it’s not like you forced to caching or no caching. You can already force update intervals – just not on a domain level. 

Link to post
Share on other sites

Thank you for your replay @opentype, I figured "Feedback and Ideas" would be the best board for feature requests. Apparently not...

Furthermore you're right. We could apply a cache time, but one of our main purposes of the cache is images not disappearing from our boards, after the source has been removed. So considering pros and cons it is not really what we're looking for.

Edited by Sledge FTB
typo
Link to post
Share on other sites

FWIW, while this request specifically hasn't been implemented, a new option in 4.4 has been added to only use the image proxy caching if the requested domain is not already secure. This may help solve the issue in a different manner.

The image proxy was originally implemented to allow you to serve images from non-secure sources, securely (so you don't get the broken padlock in your browser). That said, it has always been a 100% on or off setting, but beginning with 4.4 you can now either serve all images, no images, or only insecure images through the proxy. If you switch to insecure images only, and your tickers are served from secure domains, they will no longer be routed through the image proxy.

Link to post
Share on other sites
  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...

Important Information

We use technologies, such as cookies, to customise content and advertising, to provide social media features and to analyse traffic to the site. We also share information about your use of our site with our trusted social media, advertising and analytics partners. See more about cookies and our Privacy Policy