Forum OpenACS Q&A: Re: adding header to resource files: cache-control max-age=NNNN

Collapse
3: Re: adding header to resource files: cache-control max-age=NNNN (response to 2)
Posted by Benjamin Brink on 02/13/15 08:11 PM
Thank you, Gustaf.

Good idea to make it a parameter, since it is commonly preferred when delivering files to small/mobile devices.

cheers,

Ben

Collapse
4: Re: adding header to resource files: cache-control max-age=NNNN (response to 3)
Posted by Gustaf Neumann on 05/15/15 04:28 PM
The head version of OpenACS has now a package parameter for kernel named ResourcesExpireInterval for specifying the expiration interval for /resources/*. Per default, no expiration interval is set.
Collapse
5: Re: adding header to resource files: cache-control max-age=NNNN (response to 4)
Posted by Benjamin Brink on 05/15/15 04:53 PM
Excellent! Thank you, Gustaf.
Collapse
6: Re: adding header to resource files: cache-control max-age=NNNN (response to 4)
Posted by Cesareo Garci­a Rodicio on 11/06/15 06:26 PM
Related with this but with Content Repository. I was looking to specify Expires: header to images (photo-album) and modify
/packages/acs-content-repository/tcl/revision-procs.tcl [See below]. Please take in mind that perhpas this is not the best solution.

Would it a good idea to add a ResourcesExpiralInterval to Content Repository Parameters?

--------------------------------------
index 88c68b7..6a690ab 100644
--- a/packages/acs-content-repository/tcl/revision-procs.tcl
+++ b/packages/acs-content-repository/tcl/revision-procs.tcl
@@ -57,6 +57,10 @@ ad_proc -public cr_write_content {
set content_length 0
}

+# Based on http://www.openacs.org/forums/message-view?message_id=4231862
+ ns_setexpires [expr {60*60*24*30}]
+ns_log warning "Setting Expires en $storage_type $revision_id"
+
switch $storage_type {
text {
set text [db_string write_text_content ""]

Collapse
7: Re: adding header to resource files: cache-control max-age=NNNN (response to 6)
Posted by Gustaf Neumann on 11/11/15 09:39 AM
Dear Cesareo,

using expire for file in the content repository is much more problematic than for resources. When an end-user updates a file in the content-repository (say in file-storage, or wiki) then one expects that all user sees this change as well more or less immediately. With expires, people will see for a while the outdated files, which are served from local caches (unless they force a reload). Furthermore, the requirement of different applications of the content repository are different (e.g. photo-album, of different kind of file-storages). So having a single expire time for all usages of the file-storages is not advisable.

Collapse
8: Re: adding header to resource files: cache-control max-age=NNNN (response to 7)
Posted by Cesareo Garci­a Rodicio on 11/12/15 12:48 AM
My case scenario is mainly with photo-album. So it would be a good idea to use a parameter per package.

I'll change it in my setup to use only inside photo-album. Thanks 😉

Collapse
9: Re: adding header to resource files: cache-control max-age=NNNN (response to 8)
Posted by Cesareo Garci­a Rodicio on 11/13/15 10:41 PM
Just to keep documented here. I'm using it now in photo album to serve images (6 months cache)

diff --git a/packages/photo-album/www/images/index.vuh b/packages/photo-album/www/images/index.vuh
index ce37de7..2a567bd 100644
--- a/packages/photo-album/www/images/index.vuh
+++ b/packages/photo-album/www/images/index.vuh
@@ -18,6 +18,10 @@ if {[parameter::get -parameter CheckPermissionOnImageServeP] == "t"} {
permission::require_permission -object_id $image_id -privilege "read"
}

+# Based on http://www.openacs.org/forums/message-view?message_id=4231862
+# Six months expire
+ ns_setexpires [expr {60*60*24*30*6}]
+
if {[catch {cr_write_content -revision_id $image_id} errMsg]} {
if {$::errorCode eq "NOT_FOUND"} {
ns_returnnotfound