On Fri, Aug 9, 2019 at 2:37 PM Alex Rousskov <
rouss...@measurement-factory.com> wrote:
> On 8/9/19 1:37 PM, Tom Karches wrote:
> > On Fri, Aug 9, 2019 at 11:38 AM Alex Rousskov wrote:
>
> > Ok, here is the info from the real trace. First time with #dns_v4_first
> > on commented out, 2nd time "dn
On 8/9/19 1:37 PM, Tom Karches wrote:
> On Fri, Aug 9, 2019 at 11:38 AM Alex Rousskov wrote:
> Ok, here is the info from the real trace. First time with #dns_v4_first
> on commented out, 2nd time "dns_v4_ first on" is active. Difference is
> with no "dns_v4_first on" directive, I get a RR_CONNECT
On Fri, Aug 9, 2019 at 11:38 AM Alex Rousskov <
rouss...@measurement-factory.com> wrote:
> On 8/9/19 9:59 AM, Tom Karches wrote:
>
> > With this command :
> > $curl --trace --proxy http://127.0.0.1:3128 https://www.google.com
>
> > Invalid URL
>
> Yeah, that command does not do what you think it d
On 8/9/19 9:59 AM, Tom Karches wrote:
> With this command :
> $curl --trace --proxy http://127.0.0.1:3128 https://www.google.com
> Invalid URL
Yeah, that command does not do what you think it does. This has bitten
me many times. You may want to remove the file name "--proxy" now :-).
Hint: The
>
>
> On 8/8/19 3:29 PM, Tom Karches wrote:
>
> > I am in the process of upgrading our Squid proxy server from 3.1 (on
> > RHEL6) to 3.3 (on RHEL7).
>
> It could have been worse! For example, you could ask a question about
> upgrading Squid from v1.0 to v2.0... I will try to help, but I do not
> re
