As designed Image Proxy doesn't respect cache headers

[md_5]

Images shouldn't be cached for longer than the Cache-Control header specifies.

 

[Mike]

While I appreciate the sentiment, this is really the designed behavior for the image proxy. It's not designed to be a simple client-side cache and disabling caching (for example) could very easily lead to a degraded experience (slow servers) and potentially a significant bandwidth increase.

 

[md_5]

While I appreciate the sentiment, this is really the designed behavior for the image proxy. It's not designed to be a simple client-side cache and disabling caching (for example) could very easily lead to a degraded experience (slow servers) and potentially a significant bandwidth increase.

The problem I have is that many users (especially in their signatures) have dynamic images that change on a frequent basis, yet the image proxy is needed for full https integration.
Maybe the cache time could be set:

cacheTime = (cacheHeader < minCache) ? minCache : ((cacheHeader < maxCache)? cacheHeader : maxCache);

That way everything gets cache for at least some period, and those which need to be refreshed frequently can be.

 

[McLive]

Any news about this?

 

[Paul B]

News in what sense?

As the prefix denotes, this is as designed.