Setting the HTTP Cache-Control header to "private" improves system performance when loading dynamic VoiceXML 2.0 content.


By default, any dynamic VoiceXML 2.0 content is cached in Blueworx Voice Response unless the Cache-Control HTTP header field is set correctly.
This can cause performance problems as the dynamic content cannot be reused from the cache. Instead, it has to be fetched and cached again from scratch each time it is referenced.


Resolving the problem

Set the Cache-Control field in the HTTP header to "private" or "no-cache". The method for achieving this is application-specific, but as an example, including the following line in a WebSphere Application Server JSP sets the HTTP header:

<res:setHeader name="Cache-Control">private</res:setHeader>