What happens is that the file-cache is located in /../ (the folder below the web root). Unwanted for sure. So. Can i force it to a different folder, like /data/www.domain.ext/ ?
You can't set the location of the cached files, but you have stumbled onto a bug in 2.5.2 when using remote domains. The cached images should be stored in /data/cached/www.domain.ext but what happens with the bug is that when the <ImageBaseDir> contains the http:// the cached image goes in the same folder as the imagegen.ashx file rather than the /data/cached/yourdomain folder.
A workaround would be to include the http://domain as part of the ?image= querystring parameter. Or to use a url rewrite rule to add the http://domain to the querystring without having to specifically add it to the querystring for each imagegen.ashx request.
Location of cached remote images when using <ImageBaseDir>.
Hi,
Is it possible to set the location of cached remote files?
Im using the ImageBaseDir config key, set to something like <ImageBaseDir>http://www.domain.ext/folder/</ImageBaseDir>;.
What happens is that the file-cache is located in /../ (the folder below the web root). Unwanted for sure.
So. Can i force it to a different folder, like /data/www.domain.ext/ ?
Anders
Hi, Anders,
You can't set the location of the cached files, but you have stumbled onto a bug in 2.5.2 when using remote domains. The cached images should be stored in /data/cached/www.domain.ext but what happens with the bug is that when the <ImageBaseDir> contains the http:// the cached image goes in the same folder as the imagegen.ashx file rather than the /data/cached/yourdomain folder.
A workaround would be to include the http://domain as part of the ?image= querystring parameter. Or to use a url rewrite rule to add the http://domain to the querystring without having to specifically add it to the querystring for each imagegen.ashx request.
cheers,
doug.
Ok, i used the ?image= querystring parameter earlier and that was fine.
However it would be great to be able to use the BaseUrl.
Whats the timeline for getting it fixed?
Anders
I see that it is solved in 2.5.6.
Excellent work!
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.