Forum Discussion
rb1980_75708
Nimbostratus
Nimbostratusdeciphering X-PvInfo
Can anyone point me to some resourses on how to decipher the X-PvInfo headers?
I'm sure it's in the docs somewhere but cant seem to find it.
I'm setting up some new webacc boxes and would like to inspect these headers for troubleshooting.
Better yet, would be an iRule to insert the same data in human-readable format...
- Information on deciphering the pvinfo codes can be found at askf5
https://support.f5.com/kb/en-us/solutions/public/7000/100/sol7116.html?sr=477727 
rb1980_75708Thanks, I have read that document. I still found it annoying that there is no easy way to determine the 'C' code to figure out which policy you're hitting (I have several). The way I was able to find them was by going to:
/usr/local/wa/config/policies/localhost:8081/
and running:
grep "policyInstance id=" *.xml | awk '{print $7 " " $8}'- rb1980_75708PS: F5 developers, if you're reading this...
It would be a nice feature to show this in a popup at the top level of the policy tree like you do for the A codes. - The C code refers to the application that the request matches is to as an individual policy can be assigned to multiple applications. You can see the value of an application by mousing over it and viewing the URL in the status bar. The query parameter recID is the C code. Actually it is usually off by 1 from the C code in the pvinfo (not sure why this is off). I will submit an RFE to have a pop-up when scrolling over an application number that shows the actual C value.
- rb1980_75708I guess my confusion lies in the explaination in the above referenced document:
The C code is the second field of the X-PvInfo header. It indicates the number of the policy that was applied to the request. The C code is also part of the path where cached objects are stored on disk. This code also identifies the specific application used.
