HTTPS was designed to cause a transparent proxy to fail (that was one of the major design goals, no third party [such as squid] could read to the traffic). As mentioned before, to make this work, you must either drop the requirement that the proxy be transparent (Note, explicit proxies can be auto configured, and this is default state of IE and Chrome on Windows.), or you will need to drop the requirement for a caching proxy (squid) and just block on IP or DNS name.
Walter On Thu, Jun 26, 2014 at 7:19 AM, Martin Fuchs <[email protected]> wrote: > It is also not legal everywhere ;-) > > -----Ursprüngliche Nachricht----- > Von: List [mailto:[email protected]] Im Auftrag von Ryan > Coleman > Gesendet: Donnerstag, 26. Juni 2014 14:00 > An: pfSense Support and Discussion Mailing List > Betreff: Re: [pfSense] https transparent proxy project failed... > > Typically that would because no one here has experience with it and you > should try to find another resource. > > > > On Jun 26, 2014, at 2:45, A Mohan Rao <[email protected]> wrote: > > > > i think squid3-dev https transparent proxy project failed... > > still no body gave positive feedback. > > > > > > > > Thanks > > > > Mohan > > _______________________________________________ > > List mailing list > > [email protected] > > https://lists.pfsense.org/mailman/listinfo/list > _______________________________________________ > List mailing list > [email protected] > https://lists.pfsense.org/mailman/listinfo/list > > _______________________________________________ > List mailing list > [email protected] > https://lists.pfsense.org/mailman/listinfo/list > -- The greatest dangers to liberty lurk in insidious encroachment by men of zeal, well-meaning but without understanding. -- Justice Louis D. Brandeis
_______________________________________________ List mailing list [email protected] https://lists.pfsense.org/mailman/listinfo/list
