I'm not sure from which side your question was more intended; the actual HTTP code or what makes something cacheable for a caching device like a Cisco Cache Engine so I'll try to answer this from both perspectives.
There is a way to flag a HTTP document as 'non-cachable' in the HTML code. When a caching device sees this it will not write that to object to its cache. This makes frequently updated sites like news or weather sites work with caching devices.
As for non-cacheable port 80 content, I know the Cisco Cache Engine can be tweaked to cache just about anything aside of objects that are set as 'non cahceable' in the HTML code including CGI scripts (caching of CGI objects is disabled by default).
Also from the caching device's perspective there are several methods of flagging traffic to specify what is cacheable and non-cacheable. You can create bypass lists by source or destination IP address, layer 5 regular expression matches, ect.
Moquery is the command line cousin of Vizore, it's very helpful and efficient sometimes during the troubleshooting. This article aims to provide moquery cheat sheet to the users for some most common seen scenarios.
Here is the checklist before customers/partners contact Cisco TAC:
Firmware Version of APIC and Switch
Download Switch and APIC techsupport logs
Problem description (Symptoms with details)
Business impact (eg, what kind of services...
moquery usageAPIC moquerySwitchmoquery
This document discuss a common issue observed during the VMM integration & VM workload migration to ACI fabric.
VMware Virtual machines are hosted in Cisco UCS-B seri...