For those who haven’t had a chance to examine the file at length, the globalfragment.xml file is basically a roadmap that the WebAccelerator module can read to know how to handle or classify different file types.  If you want the WebAccelerator recognize and classify a particular file type it would be good for it to be defined in this file.

If you take the upgrade path I mentioned above, it might be wise to make a backup copy of that particular file first.  The file can be found in the “/config/wa/” directory.  It is possible for that file to be overwritten during the upgrade and if you have custom entries defined in it… well you get the picture!

Unbeknownst to me, custom entries had been inserted into that file for .wmv files at some earlier date.  Shortly after the upgrade of course, .wmv files stopped streaming properly from virtual servers utilizing WebAccelerator based HTTP class profiles.  So I took the profiles off the virtual servers in question and contacted F5 Networks Support.  I was unaware of how the WebAccelerator module used the globalfragments.xml file until I was educated by an excellent F5 Networks Senior Network Support Engineer about it.

I added the entries back for the .wmv files, reapplied the HTTP class profiles that I had disabled during troubleshooting and everything worked like a charm.  The Engineer was also kind enough to create CR12834 to add .wmv files to the stock list of file types into future TMOS versions.  Thanks again to Dale Anderson for all your help!

If you are having trouble with certain file types after applying a WebAcceleration HTTP class profile then you might take a peek at the globalfragments.xml file and ensure the file type is defined correctly within.

This issue and the one mentioned in my previous post are the only two issues that I had from upgrading from version 9.4.4 to version 9.4.8!