Loading Policy Configuration in the Local File
10 February, 2008 by Greg Ferro Print Posting
A common question in the Blue Coat forums is “how do I load this config snippet into configuration. The question most often comes from people who are new to SGOS and have been using the Virtual Policy Manager. This quick note shows you how to load a config snippet that removes the X-Bluecoat-Via header
You have been reading the Blue Coat forums and someone has given you a piece of config that you need to use. This post shows you how to load the config snippet
Step 1 - Go to Configuration, Policy, Policy Files and select the drop down box ‘Install local file from’ as per the screenshot below”
This will open a simple window that allows for very simple text. You need to be careful about your syntax here, because this text is the actual Blue Coat CPL* programming language. now insert the text as shown
and when you click on install, the CPL will parsed by the compiler. If it passes the compiler it will report a success message.
You can now test to confirm that this working as you expected.
*(Content Policy Language)
It’s Visual Policy Manager, not Virtual
You’re visually editing the policy with a GUI instead of manually using the text-based content policy language like you are in this example.
As for the X-Bluecoat-Via header… perhaps you could explain what it actually does and then let someone decide for themselves if they really want to remove it. Basically there are several situations where a request loop occurs, where Proxy A forwards a request to Proxy B who forwards it to Proxy C who forwards it back to Proxy A… the proprietary header was added to prevent such a looping scenario with a little more power than the standard Via header.
That said, if you still want to stop this for some reason, while what you have is one way to do it, the more correct (and more efficient) way to do it is in the CLI interface.
Blue Coat SG200 Series# conf t
Blue Coat SG200 Series#(config)http no proprietary-headers bluecoat
-B
Yes, I mention this in a more detailed post at http://etherealmind.com/2008/02/27/delete-the-http-header-bluecoat-x-via-on-your-proxy/.
Thanls for the tip on the new HTTP command. Can you confirm which version this was introduced ?
Seems command ‘http no proprietary-headers bluecoat’ has no effect.
What version of code are you running ?