Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I've been using request tracker v4.0.8, over a relatively high latency internet connection, and I noticed that many (all?) of the supposedly static resources (css, javascript, images) are located in a /NoAuth/ directory.

The CSS and javascript for each page are generated by RT on each request, and are served with Cache-Control: no-cache. The images and additional requests generated by those files (misc images, more css, etc) are also no-cache. This all seems rather wasteful, to me.

Is there some trick or configuration that I can use to make RT operate in a less cache-hostile way?

share|improve this question

As recommended in the RT web deployment documentation, Apache should be configured with

Alias /NoAuth/images/ /opt/rt4/share/html/NoAuth/images/

The equivalent in nginx is

location /NoAuth/images {
    root /opt/rt4/share/html;

... and in lighttpd it is

alias.url = (
    "/NoAuth/images/" => "/opt/rt4/share/html/NoAuth/images/",
share|improve this answer
Yes, I've already done that. I suppose I should have mentioned that in my question. The problem is that there are a lot of resources that are either referenced by CSS or loaded dynamically via javascript, and they are not cached. Images don't seem to be my problem, it's apparently un-cacheable CSS and JS. – vezult Jun 17 '13 at 0:49

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.