Hi Damitha. Welcome to the forums. Are you able to replicate (or confirm) this problem is happening on the same workstation with all three web browsers involved? Is there an explicit web proxy enabled on the Fortigate and/or on the network? (Are all 3 browsers on the workstation configured to use the same network or proxy settings?) Doubt this could be what' s happening in your case (thought curious to know if it is) but something that was pointed out in this thread that Google Chrome (and Firefox) are starting to use SPDY if a website like Facebook supports it.
NSE4/FMG-VM64/FortiAnalyzer-VM/6.0 (FWF30E/FW92D/FGT200D/FGT101E/FGT81E)/ FAP220B/221C
At the moment I see this issue only by accessing facebook. Other sites are blocking perfectly.In that case, I would check the web filter/Ratings Override/app sensors that is applied to web traffic to see if facebook have not inadvertently been allowed somewhere. Edit: scratch that. If problem is only happening in Chrome and Firefox but not in IE then the problem is may be something else. Perhaps maybe just blocking facebook outright via fqdn (one each for facebook.com, www.facebook.com, s-static.ak.facebook.com) at the firewall level as a temp solution for now.
NSE4/FMG-VM64/FortiAnalyzer-VM/6.0 (FWF30E/FW92D/FGT200D/FGT101E/FGT81E)/ FAP220B/221C
There is only one Internet Link. one Firewall. No any other proxies. I tried with different workstations but result is same. All browsers share same proxy settings. (No Proxy) At the moment I see this issue only by accessing facebook. Other sites are blocking perfectly.Can you access facebook via the following URL in IE: https://www.facebook.com ? If so, you can stop here and post a response. If not, continue... Can you run the following debug command, accessing facebook on chrome and post the output: 1) Start debugging:
diag debug flow filter clear diag debug reset diag debug enable diag debug flow show console enable diag debug flow filter addr 192.168.100.2 #[where ' 192.168.100.2' is the IP address of the client you will be testing access from] diag debug flow show function-name enable diag debug flow trace start 5002) Access facebook in chrome on 192.168.100.2 3) Stop debugging:
diag debug flow show console disable diag debug flow trace stop diag debug flow filter clear diag debug disable diag debug resetThis determines which policy the packets are being qualified for, and will pinpoint which web filter policy is affecting traffic. Thanks, Matt
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 2024 Fortinet, Inc. All Rights Reserved.