Cisco Bug: CSCur32547 - VXML Gateway HTTP Request should compare etag field for WAV update
Jul 31, 2017
- Cisco 3900 Series Integrated Services Routers
Known Affected Releases
Symptom: Customer changed the WAV. The WAV remains the same name and stored in the same location. No other action was performed after the change of WAV name, such audio load, set http client cache stale commands on the router. The new WAV is not played or get updated on IOS GW Conditions: New/Replaced WAV file has same name and Last-Modified date is older. eg Old SOM_E_en-US_1000-001.wav has Last-Modified: Sat, 04 Oct 2014 15:16:14 GMT New SOM_E_en-US_1000-001.wav has Last-Modified: Sat, 20 Sep 2014 20:17:47 GMT Because of the Old WAV had a newer Last-Modified date, Client IOS is receiving a ?Message Response Code: 304? and is not triggering the new WAV update.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.
Bug Details Include
- Full Description (including symptoms, conditions and workarounds)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases