[squid-users] SSL tunnel for soon to go Live site not working

From: IggyDolby <IggyDolby_at_hotmail.com>
Date: Mon, 7 Oct 2013 07:01:23 -0700 (PDT)

Hi I'm a Squid newbie and need to configure Squid to proxy HTTP and HTTPS
(Tunnel) requests from external users on Browsers and iPads and resolve to
an IP address were the DNS has not been switched yet.
We can manually change the iPads proxy configuration to point to this proxy.
The site has a Browser popup authentication on the first redirect from HTTP
to HTTPS.
I never see the browser popup....
I am able to configure Squid properly I believe for HTTP proxy

But when I request and HTTPS page I get this error:

1381116961.902 0 xxx.xxx.xx NONE/400 3841 CONNECT
error:method-not-allowed - NONE/- text/html

On an HTTP request I actually get the page:
1381116975.786 60 xxx.xxx.xx TCP_MISS/200 551 GET
http://m.xxxxxxx.com/healthcheck/healthcheck.html - FIRST_UP_PARENT/myAccel
text/html

This is my squid.conf

# Recommended minimum configuration:
#
acl manager proto cache_object
acl localhost src 127.0.0.1/32 ::1
acl to_localhost dst 127.0.0.0/8 0.0.0.0/32 ::1

# 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 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 8080 # http
acl CONNECT method CONNECT
acl SSL method CONNECT

acl our_sites dstdomain m.xxxxx.com
http_access allow our_sites
cache_peer xx.xx.xx.xx parent 80 0 no-query originserver name=myAccel
cache_peer_access myAccel allow our_sites
cache_peer_access myAccel deny all

#
# Recommended minimum Access Permission configuration:
#
# Only allow cachemgr access from localhost
http_access allow manager localhost
http_access deny manager

# 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

# 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 80 defaultsite=m.xxxxx.com
never_direct allow all

# We recommend you to use at least the following line.
hierarchy_stoplist cgi-bin ?

# 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 .

--
View this message in context: http://squid-web-proxy-cache.1019090.n4.nabble.com/SSL-tunnel-for-soon-to-go-Live-site-not-working-tp4662462.html
Sent from the Squid - Users mailing list archive at Nabble.com.
Received on Mon Oct 07 2013 - 14:02:06 MDT

This archive was generated by hypermail 2.2.0 : Tue Oct 08 2013 - 12:00:21 MDT