11th February 2012

You are here: Home / Blog / Operation / Blue Coat / Loading Policy configuration in the Local file

Loading Policy Configuration in the Local File

10th February 2008 By 5 Comments

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”

bct-policy-local-file1.png

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

bct-policy-local-file2.png

and when you click on install, the CPL will parsed by the compiler. If it passes the compiler it will report a success message.

bct-policy-local-file3.png

You can now test to confirm that this working as you expected.

*(Content Policy Language)

This post is copyright of Thropos Ltd ©2008-2011 at Etherealmind.com - contact | email: greg.ferro@packetpushers.net - twitter: @etherealmind | All rights reserved
Filed Under: Blue Coat Tagged With: , ,
About Greg Ferro

Greg Ferro is a Network Engineer/Architect, mostly focussed on Data Centre, Security Infrastructure, and recently Virtualization. He has over 20 years in IT, in wide range of employers working as a freelance consultant including Finance, Service Providers and Online Companies. He is CCIE#6920 and has a few ideas about the world, but not enough to really count.

He is a host on the Packet Pushers Podcast, blogger at EtherealMind.com and on Twitter @etherealmind and Google Plus

  • Bill

    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

  • Sam

    Seems command ‘http no proprietary-headers bluecoat’ has no effect.

    • http://etherealmind.com Greg Ferro

      What version of code are you running ?

  • Pingback: Delete the X-Bluecoat-Via Header on your ProxySG — My Etherealmind