2 way SSL on a non standard SSL Port

Bart Spedden <bart.spedden@xxxxxxxxxxxxxx> · Tue, 24 Nov 2015 15:41:48 -0700

Hello,
I have a java application that is successfully making REST calls to a 3rd party vendor that requires 2 way SSL on port 8184 for some calls and 1 way SSL on port 8185 for other calls. However, when I start proxying the calls with squid all 1 and 2 way SSL calls fail. 

I added ports 8184 and 8185 to both SSL_Ports and Safe_ports via the following:

acl SSL_ports port 8184
acl SSL_ports port 8185

acl Safe_ports port 8184
acl Safe_ports port 8185

Here's a little config information 

squid -v
Squid Cache: Version 3.4.3

Here's my full configuration:

#
# Recommended minimum configuration:
#

# Example rule allowing access from your local networks.
# Adapt to list your (internal) IP networks from where browsing
# should be allowed
acl localnet src 10.0.0.0/8	# RFC1918 possible internal network
acl localnet src 172.16.0.0/12	# RFC1918 possible internal network
acl localnet src 192.168.0.0/16	# RFC1918 possible internal network
acl localnet src fc00::/7       # RFC 4193 local private network range
acl localnet src fe80::/10      # RFC 4291 link-local (directly plugged) machines

acl SSL_ports port 443
acl SSL_ports port 8184
acl SSL_ports port 8185
acl Safe_ports port 80		# http
acl Safe_ports port 21		# ftp
acl Safe_ports port 443		# https
acl Safe_ports port 70		# gopher
acl Safe_ports port 210		# wais
acl Safe_ports port 1025-65535	# unregistered ports
acl Safe_ports port 280		# http-mgmt
acl Safe_ports port 488		# gss-http
acl Safe_ports port 591		# filemaker
acl Safe_ports port 777		# multiling http
acl Safe_ports port 8184
acl Safe_ports port 8185
acl CONNECT method CONNECT

#
# Recommended minimum Access Permission configuration:
#
# Deny requests to certain unsafe ports
http_access deny !Safe_ports

# Deny CONNECT to other than secure SSL ports
http_access deny CONNECT !SSL_ports

# Only allow cachemgr access from localhost
http_access allow localhost manager
http_access deny manager

# We strongly recommend the following be uncommented to protect innocent
# web applications running on the proxy server who think the only
# one who can access services on "localhost" is a local user
#http_access deny to_localhost

#
# INSERT YOUR OWN RULE(S) HERE TO ALLOW ACCESS FROM YOUR CLIENTS
#

# Example rule allowing access from your local networks.
# Adapt localnet in the ACL section to list your (internal) IP networks
# from where browsing should be allowed
http_access allow localnet
http_access allow localhost

# And finally deny all other access to this proxy
http_access deny all

# Squid normally listens to port 3128
http_port 3128

# Uncomment and adjust the following to add a disk cache directory.
#cache_dir ufs /var/spool/squid 100 16 256

# Leave coredumps in the first cache dir
coredump_dir /var/spool/squid

#
# Add any of your own refresh_pattern entries above these.
#
refresh_pattern ^ftp:		1440	20%	10080
refresh_pattern ^gopher:	1440	0%	1440
refresh_pattern -i (/cgi-bin/|\?) 0	0%	0
refresh_pattern .		0	20%	4320

Any help is greatly appreciated!

Thanks!
-- 
Bart Spedden  |  Senior Developer
+1.720.210.7041  |  bart.spedden@xxxxxxxxxxxxxx

3 | S H A R E  |  Adobe Digital Marketing Experts  |  An Adobe^® Business Plus Level Solution Partner
Consulting  |  Training  |  Remote Operations Management

_______________________________________________
squid-users mailing list
squid-users@xxxxxxxxxxxxxxxxxxxxx
http://lists.squid-cache.org/listinfo/squid-users