Tickets :: Comment on [#13070] Deterministic Asset Names

* Your Email Address
* Spam protection	Enter the letters below: .__..__ .__ . ..__. \| \|[ __[__)\|_/ \| \| \|__\|[_./\| \\| \\|__\
Comment	> hey, thanks for the fast reply. making the path configurable is quite > nice in it self, but i meant something slightly different. > > my initial problem was the following: > > i have several horde installations behind a load-balancer. this one > uses session-binding to redirect a certain user to a certain backend. > > now i tried to serve the static assets through a different pipeline > than the rest. so i configured a reverse-proxy to deliver them. since > its only static assets i figured i don't need the session binding and > it can fetch the assets from an arbitrary backend. > > but since the assets (e.g. compressed js files) seem to be randomly > named, when the request for assets goes to an arbitrary backend, they > will not match the filenames produced by the replying horde instance. > > of course i could just collect all assets and serve them from a > separate place (that's probably what i'll do), or as you suggest in > the conf.xml place the assets directory on a nfs share. but still i > figured it would be nice if the assets had a deterministic name, then > this would not be necessary. > > additionally it would improve cache efficiency, since random names > also means that every asset has to be cached once per backend on a > reverse-proxy.
Attachment
Watch this ticket