Route is not being set for hit in 1.13.1.0?
mpchadwick opened this issue · comments
Hmm...On the store in question we are using Elastera_EnterprisePageCacheSSL which is documented to be implemented by changing the <ee> request processor.
The problem in this case appears to be that our processor extends Enterprise_PageCache_Model_Processor, rather than Elastera_EnterprisePageCacheSSL_Model_Processor causing the metadata reads to fail..
A solution was implemented here 544315b