While there is nothing you can do in the face of misconfigured
caching proxies, you can always provide proxies with some
guidance on what you do/don't consider cacheable. There's a
rather long thread at
https://openacs.org/bboard/q-and-a-fetch-msg.tcl?msg_i
d=0003PI covering this, but the short version is
"try putting
ns_set put [ns_conn outputheaders] "Cache-Control" "private"
ns_set put [ns_conn outputheaders] "Pragma" "no-cache"
in your master template"
