> I'm proxying upstream's view on this. > > 08:12 < muks> jordi: i think i follow his bug report only now.. he is > filtering > by domain, not url and asking why he's getting differing results > for HTTP and HTTPS requests > 08:13 < muks> i think tinyproxy can't do any better than deny the request > without any errors, because when the browser wants to connect > using 'https://', it tries to start an SSL negotiation > 08:14 < muks> tinyproxy doesn't do any SSL.. it doesn't link to openssl, > > etc. > adding all this just for error pages would make it ave a bulky > footprint > Jordi Mallach <jo...@xxxxxxxxxx>
Maybe we could introduce this functionality as a module. That way, the core application would remain small, but the facility to filter SSL websites would be available for those that needed it. There are lots of important websites that use SSL, and causing the web browser to wait for infinity is not really a satisfactory solution. > 08:20 < muks> an admin would have to configure it with SSL certificates, etc.) That would be no problem. Proxomitron used to do this (but it was Microsoft Windows based). > 08:20 < muks> it's too much of mish-mosh for very little gain Well, it makes the difference between being able to use the proxy or not. The gain is that we can browse the internet and filter content from unwanted providers, which is one of the primary reasons for using a proxy. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
