| CPUG | |
| The Check Point User Group | |
| A Resource For The Check Point Community. Fast. Useful. Independent. | |
|
| |||||||
![]() |
| | LinkBack | Thread Tools | Display Modes |
| |||
| Hi We are browsing through a http blue coat proxy, http sites are fine but browsing to any https site fails with CONNECT Command found in HTTP request. Looking at resolutions for this it states to switch off CONNECT checking as part of the web intelligence HTTP methods tab but after doing this, saving the changes and pushing the policy i still get the same error. We are using Checkpoint VSX NGX R60A. Thanks in advance Mac |
| |||
| You could disable SMDF for the gateway (under the gateway object) and see if this is SmartDefense related. If the error still occurs, it may be due to the protocol type & its settings for the services in the rule of the drop. If turning off SMDF allows the traffic to pass, then there are additional SMDF checks you need to disable. In the past, with an HTTP illegal header drop I was seeing, I've found that merely disabling the check did not disable it for other SMDF checks. I had to disable all SMDF which related to the inspection of HTTP traffic. You can find that list in this CPUG thread. HTH __________________ Its all in the documentation. |
| |||
| Ah, my apologies. I'm abbreviating SmartDefense into SMDF, and I realize now that it may only be an R65 setting. Under the object properties for the gateway between NAT and VPN you may have a "SmartDefense", if you highlight that you should have an option to "Do not apply SmartDefense on this gateway". If you cannot do this step then you will need to proceed to turn off specific SMDF checks until you no longer see the traffic drop, then you will know which SMDF checks were the problem. __________________ Its all in the documentation. |
![]() |
| Thread Tools | |
| Display Modes | |
| |