I guess I badly explained myself. The problem is that the CSS removes automatically all HTTP headers. When sniffing before CSS, headers are present, after CSS they are gone. I understand encryption should bring problems for caching but I guess it can be solved too!
Cache device in this case is the cache of the client browser. You can check it out on information page of Firefox. Everything are noted as no-cached.
I guess this is a very strange problem. Thank you for interesting to my problem!
Thanks for your response but I understand a middle device wont be able to cache because he doesnt have the session key. But in case of client's browser, it's not true! All clients are able to cache encrypted page (except if corresponding option has been disabled). In Content Switch system, connection is unsecure between server and CSS. The SSL layer is built only between CSS and client. Thus, CSS see the clear HTTP packet. In consequence, he is able to withdraw HTTP header. That's my problem! I dont want my CSS to remove HTTP header! Since he removes it, cache header are removed and caching is thus disabled... In some kind, it seems the CSS builds a new HTTP answer retrieving only data field of the received from the server. I really dont understand what's happening!
Topology & Design:
Two ACI fabrics
Stretching VLANs using OTV
Both fabrics are advertising BD subnets into same routing domain
Some BDs(or say VLANs) are stretched, but some are not.
Endpoints can move betwee...
VMware Trunk Port Group is supported from ACI version 2.1
VMM integration must be configured properly
ASA device package must be uploaded to APIC
ASAv version must be compatible with ACI and device package version
Topology &Design:Traffic flow within same fabric:Endpoint moves to Fabric-2Bounce Entry Times OutTraffic Black-holedSummarySolutionAppendix:
In the Previous articles of ACI Automation, we are using Postman/Newman a...