Skip to main content

LevelBlue Completes Acquisition of Cybereason. Learn more

LevelBlue Completes Acquisition of Cybereason. Learn more

Services
Cyber Advisory
Managed Cloud Security
Data Security
Managed Detection & Response
Email Security
Managed Network Infrastructure Security
Exposure Management
Security Operations Platforms
Incident Readiness & Response
SpiderLabs Threat Intelligence
Solutions
BY TOPIC
Offensive Security
Solutions to maximize your security ROI
Operational Technology
End-to-end OT security
Microsoft
Unlock the full power of Microsoft Security
Securing the IoT Landscape
Test, monitor and secure network objects
Why LevelBlue
About Us
Awards and Accolades
LevelBlue SpiderLabs
LevelBlue Security Operations Platforms
Security Colony
Partners
Microsoft
Unlock the full power of Microsoft Security
Technology Alliance Partners
Key alliances who align and support our ecosystem of security offerings
Loading...
Loading...

FAQ: HTTPS Filtering and Block Pages

Expand / Collapse


This article applies to:

  • R3000 All Versions

Question:

  • Why don't I get a block page when I am trying to access a blocked https site?

Reply:

Because of the nature of https connections it's often times not possible to send a block page to the end user after an HTTPS connection has been made with the website. The browser will not honor a TCP redirect from a secure website (the https site) to an unsecured website (the block page). The block page is only successfully delivered if the filter is able to send the redirect before the browser complete the TCP handshake with the website.

Instead of the Web Filter block page you will see an error message which will vary depending on the browser type.

Notes:

 


To contact LevelBlue about this article or to request support:


Rate this Article:
     

Add Your Comments


Comment submission is disabled for anonymous users.
Please send feedback to Trustwave Technical Support or the Webmaster
.