Forum Discussion
Dev_56330
Cirrus
CirrusSharePoint and WebAcceleration
I have recently configured a SharePoint application service using the latest SharePoint iApp (running Big-IP 11.4 HF 3). The default configuration for Web Acceleration creates a profile using optimi...
The WAM application stats are really the only thing to look at other than the header. It looks like some of the responses are being cached.
The X-WA-Info header should show you where the content was served from and what node of the acceleration policy it matched. There are explananations on page 77 of this guide:
https://support.f5.com/content/kb/en-us/products/wa/manuals/product/wa_implementations_11_0_0/_jcr_content/pdfAttach/download/file.res/wa_implementations_11_%20%20%20%20%20%20%20%20%20%20%200_0.pdf
If you open the acceleration policy in BIG-IP GUI, and hover over the individual leaf names in the policy tree, it will display a 5 digit number. That number corresponds to the node ID in the X-WA-Info header.
The WAM application stats are really the only thing to look at other than the header. It looks like some of the responses are being cached.
The X-WA-Info header should show you where the content was served from and what node of the acceleration policy it matched. There are explananations on page 77 of this guide:
https://support.f5.com/content/kb/en-us/products/wa/manuals/product/wa_implementations_11_0_0/_jcr_content/pdfAttach/download/file.res/wa_implementations_11_%20%20%20%20%20%20%20%20%20%20%200_0.pdf
If you open the acceleration policy in BIG-IP GUI, and hover over the individual leaf names in the policy tree, it will display a 5 digit number. That number corresponds to the node ID in the X-WA-Info header.
Dev_56330Cirrus
CirrusWell it all makes sense now. All of the responses I get are S10206 which are "Response was served from the origin web server, because the
content cannot be cached."