Summary
Question
For non-ssl situations it may, for security reasons, be necessary to set ALM to no-cache.
Mind that if SSL is implemented cache control is already set to no-cache.
Therefore this only applies to non-ssl implementations.
Answer
Procedure...
1) Navigate to the following default path...
Windows: C:\ProgramData\HP\ALM\webapps\qcbin\WEB-INF
Linux: /var/opt/HP/ALM/webapps/qcbin/WEB-INF
2) Open the file "web.xml" for editing
3) Locate the following block of text...
<servlet>
<servlet-name>default</servlet-name>
<servlet-class>com.hp.alm.platform.web.ALMDefaultServlet</servlet-class>
<init-param>
<param-name>dirAllowed</param-name>
<param-value>false</param-value>
</init-param>
</servlet>
4) Add the following text in red...
<servlet>
<servlet-name>default</servlet-name>
<servlet-class>com.hp.alm.platform.web.ALMDefaultServlet</servlet-class>
<init-param>
<param-name>dirAllowed</param-name>
<param-value>false</param-value>
</init-param>
<init-param>
<param-name>cacheControl</param-name>
<param-value>no-store</param-value>
</init-param>
</servlet>
5) Save changes
6) Bounce the ALM service