Preview Tool

Cisco Bug: CSCua84217 - Rule validated for more than one domain pattern in rule file

Last Modified

Jun 21, 2020

Products (1)

  • Cisco Content Delivery Engine Series

Known Affected Releases


Description (partial)

Before the SE  not failover when there is a read timeout on the SE due to failure on the upstream SE

When a failover occurs on the upstream SE, the transaction on the current SE could be in one of the following states - 
1. Trying to establish connection to the upstream SE
2. Connection established, trying to send (write) the request - 
3. Request Sent, Waiting for Header
4. Header Received, Receiving body 

Before the fix 
- if we were in State 1) or 2) and we receive a timeout we will go ahead and try connecting to another upstream node - SE or Origin Server (depending on topology).
- if we were in State 3) and we receive a timeout we will send a 504 to the client 
- if we were in State 4), a 200 has already been sent to the client, hence the SE silently aborts and terminates the connection
The fix changes the behavior and the SE fails over to another upstream node in all of the above cases. 

Please note that this is a corner-case and is seen only on upstream SE failure.
Bug details contain sensitive information and therefore require a account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.