[squid-users] Help troubleshooting proxy<-->client https

Masha Lifshin mlifshin at phantomdesign.com
Wed May 31 20:42:53 UTC 2017

Dear Alex,

Thank you very much for your helpful reply.

I have a follow up question.  What I am trying to achieve is an https
connection between the client and squid proxy, as well as listen on port 80
for http traffic, on port 443 for ssl traffic, and apply ssl-bump to the
ssl traffic.  I am having trouble expressing this in my config. Would the
http_port and https_port directives need to look like this?

http_port <ip_address>: <>80 ssl-bump
cert=/path/to/some.cert.pem generate-host-certificates=on
dynamic_cert_mem_cache_size=4MB tls-dh=/usr/local/squid/etc/dhparam.pem
https_port <ip_address>:443 <>

Also wondering what, if any, are the security issues with using port 80 for
the http traffic?

Thank you,

On Fri, May 26, 2017 at 7:19 AM, Alex Rousskov <
rousskov at measurement-factory.com> wrote:

> On 05/26/2017 12:00 AM, Masha Lifshin wrote:
> > I have added an https_port directive
> > to squid.conf, but it must be misconfigured.
> > http_port ...
> > https_port ...
> You are right -- your Squid is misconfigured. You cannot use the same
> address for two ports. Unfortunately, Squid thinks that port binding
> errors are a minor inconvenience and continues running after logging an
> error message (that looks like many other benign error messages).
> Changing one of the ports will solve the "same address" problem
> described above.
> Do not use port 443 for http_port. It makes triage extremely confusing
> because port 443 usually implies SSL. Consider using port 3128 instead.
> HTH,
> Alex.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squid-cache.org/pipermail/squid-users/attachments/20170531/7a3b3f2e/attachment.html>

More information about the squid-users mailing list