Hey guys... First of all say that I'm very thankful about the quick replies and advises from everyone. @Fred and @Alberto: Reading across all the thread I think that definitely going to try a 3.5.x release tomorrow and I'll report the results here. @babajaga: I use to block this kind of traffic using the domain lists generated by Shalla Secure Services (shallalist.de) and also blocks some other contents. @Eliezer I'm using Ubuntu Server 14.04 (not especial decision, because I use to deploy different distros in a Citrix XenServer test environment) Have you any guide to implements QOS+Squid? As I said, I saw in many articles that you have to mark the traffic in Squid to deal with him after but I'm never tried because didn't had enough information about. @Alberto: Happy to know about your feedback On Wed, Feb 17, 2016 at 8:19 PM, Alberto Perez [via Squid Web Proxy Cache] < ml-node+s1019090n4676071h92@xxxxxxxxxxxxx> wrote: > I can confirm that this bug is fixed in 3.5.12, I am from Cuba too, > used to have two delays, one for http and one for https with the 2x > workaround mentioned here, after my last upgrade to 3.5.12 the issue > is gone. > > Also I will highly recommend to use 3.5.x versions, there is a HUGE > difference in lot of things including SSL-BUMP, what in your case, > with that small amount of workstations, I would suggest to implement > as you could easy install the custom certificate in all of them, it > may considerably increase your HIT rate and save a lot of bandwidth > since we have too much https traffic now days. > > Kind regards > > Alberto > > > > > > On 2/17/16, FredB <[hidden email] > <http:///user/SendEmail.jtp?type=node&node=4676071&i=0>> wrote: > > > There was a know bug about delay pool and HTTPS, but as far as I know > it's > > fixed now > > you did a test with 3.5.x ? > > > > Fred > > _______________________________________________ > > squid-users mailing list > > [hidden email] <http:///user/SendEmail.jtp?type=node&node=4676071&i=1> > > http://lists.squid-cache.org/listinfo/squid-users > > > _______________________________________________ > squid-users mailing list > [hidden email] <http:///user/SendEmail.jtp?type=node&node=4676071&i=2> > http://lists.squid-cache.org/listinfo/squid-users > > > ------------------------------ > If you reply to this email, your message will be added to the discussion > below: > > http://squid-web-proxy-cache.1019090.n4.nabble.com/Delay-Pools-and-HTTPS-on-Squid-3-x-tp4676043p4676071.html > To unsubscribe from Delay Pools and HTTPS on Squid 3.x, click here > <http://squid-web-proxy-cache.1019090.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=4676043&code=c2NvcnBpb254aWlAZ21haWwuY29tfDQ2NzYwNDN8MTE2NzYzMzM3NA==> > . > NAML > <http://squid-web-proxy-cache.1019090.n4.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml> > -- View this message in context: http://squid-web-proxy-cache.1019090.n4.nabble.com/Delay-Pools-and-HTTPS-on-Squid-3-x-tp4676043p4676072.html Sent from the Squid - Users mailing list archive at Nabble.com. _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
