Cisco Bug: CSCtb84811 - Acquirer does not handle ETags with '=' correctly
Jul 14, 2015
- Cisco Enterprise CDN Software
Known Affected Releases
Symptom: The Acquirer does not handle ETag containing '=' correctly. It stops storing the ETag when it encounters a '='. This will mean that when the ACNS checks the channel content for freshness that it will give a wrong ETag in the If-None-Match field on the GET request. This will most probably cause the server to reply with a 200 'here is the data' instead of the 304 'no change'. This will cause the ACNS to download all content (that has '=' in the ETag) every time the TTL for content expires, placing a higher load on the webserver. You can check for this by using <CmdBold>cdnfs browse<noCmdBold> on the ACNS, going to the content that keeps downloading and using <CmdBold>info<noCmdBold> on the content. This will show the 'etag' value. This is the case both for weak ("W/") and normal ETag values. Conditions: Having a webserver return a '=' in the ETag value.
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