Bill ========== Fortigate 600C 5.0.12, 111C 5.0.2 Logstash 1.4.1
No protection files (that I' m aware of)Nicholas, This setting requires a Web Protection Profile in order to work per the KB. In the example in the KB, they use a sample Protection Profile called " Web" to demonstrate how you would activate this particular setting. However, if you' re not using a Web Protection Profile, what kind of inspection are you doing on your traffic? If you don' t have a web protection profile, then you are not filtering websites for any games, movies, gambling, social networking, etc. If you go to your Firewall Policy settings in the GUI and then change the Column Settings to display the Web Filter Profile, you will be able to verify if any of your traffic is already using a Web Protection Profile. That' s probably a good place to start. If you don' t use a Web Protection Profile, you could try to create a simple one with just the header exception outlined in the KB. You could try assigning that to your users to see if there is a difference. It' s easy enough to remove. Also, MR3 is now up to Patch 5. From what I' ve read, this is much more stable than Patch 3. You might want to try an upgrade as a simple first measure to see if that helps. Hope this helps.
Bill ========== Fortigate 600C 5.0.12, 111C 5.0.2 Logstash 1.4.1
Go to the UTM profiles and looking at the web filter profile that was created for us, I do not see a setting that stands out to say " scan multimedia" or " scan online streaming media" or anything like that, nor am I sure that I should.You wouldn' t see anything there. For better or worse, many of the obscure (and not so obscure) settings can only be set in the CLI. The GUI is more like a basic-to-intermediate interface to the box while the CLI is the full-monty advanced interface. If your primary web profile is called " primaryWebProfile" then you would want to make the following settings in your config to activate the header exclusions you made previously: config webfilter profile edit " primaryWebProfile" config http set options contenttype-check end config web set content-header-list 1 end next end Caveat: I am NOT using MR3, but the config for this appears to be the same. As always, make sure you backup your config before making any changes. These are pretty benign changes, but you would probably not want to make them during peak traffic.
Bill ========== Fortigate 600C 5.0.12, 111C 5.0.2 Logstash 1.4.1
config webfilter profile edit " primaryWebProfile" config http set options contenttype-check end config web set content-header-list 1 end next endFor the sake of not messing anything up, I stopped at the " config http" When I tried the command it said: command parse error before ' http' Command fail. Return code 1 Any ideas?
Created on 02-15-2012 11:18 AM
Bob - self proclaimed posting junkie!
See my Fortigate related scripts at: http://fortigate.camerabob.com
Select Forum Responses to become Knowledge Articles!
Select the “Nominate to Knowledge Base” button to recommend a forum post to become a knowledge article.
User | Count |
---|---|
1847 | |
1132 | |
769 | |
447 | |
261 |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2025 Fortinet, Inc. All Rights Reserved.