Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Squid Https blocking

    pfSense Packages
    4
    7
    5.2k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • R
      running
      last edited by

      Hello, i am running Squid/Squidguard with good result. My problem is that is is not blocking Https.
      Squid is blocking mail.yahoo.com but it is letting pass https://mail.yahoo.com

      I found this tread but no solution
      http://forum.pfsense.org/index.php/topic,11174.0.html

      Anny help?

      1 Reply Last reply Reply Quote 0
      • M
        mhab12
        last edited by

        Good find - we're seeing this too.  Hopefully someone else can find a solution, it seems like we will just need to include 443 in the transparent redirect in squid.inc.  Can someone with pf knowledge help us add that rule?

        1 Reply Last reply Reply Quote 0
        • R
          running
          last edited by

          Any update on this?

          1 Reply Last reply Reply Quote 0
          • C
            cmb
            last edited by

            You can't control HTTPS traffic that way (there is no way to see what URL you're going to, it's encrypted). You need to use firewall rules to control HTTPS. The Squid package doesn't do anything with HTTPS, it can't be cached and it can't be controlled by URL because that's all encrypted, so it doesn't touch it.

            1 Reply Last reply Reply Quote 0
            • R
              running
              last edited by

              "You need to use firewall rules to control HTTPS"

              Can you tell us how ;)

              1 Reply Last reply Reply Quote 0
              • jahonixJ
                jahonix
                last edited by

                If you just want to disallow all HTTPS traffic use a block rule for HTTPS (port: 443).

                1 Reply Last reply Reply Quote 0
                • R
                  running
                  last edited by

                  not exactly, if think it is more complicated than that.

                  If you block 443 people wont be able to go to legitimate site not block by squid.
                  Esoft seems to be able to do it and i tough that Squid was more powerful solution.

                  1 Reply Last reply Reply Quote 0
                  • First post
                    Last post
                  Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.