On 14/07/18 12:34, Krystyna Niesiołowska wrote:
> Hi All,
>
> In my company, the HR uses an outsourced SaaS (on a unique public IP)
> configured with a commercial SSL certificate (i.e. I have both the
> private and the public key) accessed by our employees via a subdomain of
> our company domain (
Hi,
I don’t get why you need a squid box for that purpose. If you have the
private key you could end the traffic on like nginx and just forward it to
saas, while doing that you could log the traffic as you want.
Best
Logan
On Fri, Jul 13, 2018 at 5:34 PM Krystyna Niesiołowska <
krystyna.niesiolo
Hi All,In my company, the HR uses an outsourced SaaS (on a unique public
IP) configured with a commercial SSL certificate (i.e. I have both the
private and the public key) accessed by our employees via a subdomain of our
company domain (saas.company.com) . Unfortunately, we cannot control the
d
On 13/07/18 13:25, Eliezer Croitoru wrote:
> I am seeing from google video links in the cache.log at squid 4.1:
>
> 2018/07/13 03:31:39 kid1| parse URL too large (10016 bytes)
>
> 2018/07/13 03:31:42 kid1| parse URL too large (10001 bytes)
>
>
>
> I will file a report later.
>
>
This has
Thanks for the help. Now I am not getting any error messages but as you
said I will follow the pull request.
Best
Logan
On Fri, Jul 13, 2018 at 8:00 AM Alex Rousskov <
rouss...@measurement-factory.com> wrote:
> On 07/12/2018 11:35 PM, login mogin wrote:
> > Thanks a lot, just tried the patch, sa
On 07/12/2018 11:35 PM, login mogin wrote:
> Thanks a lot, just tried the patch, sadly still not working.
If you still get "Unknown TLS option" errors when specifying clientca,
then you may not have rebuilt Squid correctly. If you no longer get
those errors, but Squid still does not ask the client
