Re: [squid-users] NONE/501 in an https:// POST request

* Amos Jeffries <squid3_at_treenet.co.nz>:

> >1) It's https:// -- why am I seeing the URL? Usually I'm just seeing
> > CONNECT and a target IP with HTTPS!
>
> * Possibly they were using some non-SSL capable tool or web app.
> * Maybe you have a mystery child proxy using ssl-bump feature.
>
> Either way it should work if you have SSL support built into this
> Squid. But won't if not.

I build squid-3.2.x like this:

./configure --prefix=/usr --includedir=\${prefix}/include
--mandir=\${prefix}/share/man \
--infodir=\${prefix}/share/info --sysconfdir=/etc \
--localstatedir=/var --libexecdir=\${prefix}/lib/squid3 \
--disable-maintainer-mode --disable-dependency-tracking \
--disable-silent-rules --srcdir=. --datadir=/usr/share/squid3 \
--sysconfdir=/etc/squid3 --mandir=/usr/share/man \
--with-cppunit-basedir=/usr --enable-inline --enable-async-io=8 \
--enable-storeio=ufs,aufs,diskd --enable-removal-policies=lru,heap \
--enable-delay-pools --enable-underscores \
--enable-icap-client --enable-follow-x-forwarded-for \
--enable-external-acl-helpers=ip_user,ldap_group,session,unix_group,wbinfo_group\
--enable-arp-acl --enable-snmp --with-filedescriptors=65536 \
--with-large-files --with-default-user=proxy --enable-epoll \
--enable-linux-netfilter --enable-cache-digests

am I missing something here?

  --enable-ssl Enable ssl gatewaying support using OpenSSL
  
  maybe?

> >2) Why EXACTLY is it failing? I'd like to debug this further :)
> >
>
> Possibly some bad mix of chunked encoding. But, I'm thinking the SSL
> support is missing. CONNECT does not actually involve SSL, just
> pumping bytes across a TCP tunnel link.

SSL support missing where? In Squid OR in the application that's trying
to send?

-- 
Ralf Hildebrandt
  Geschäftsbereich IT | Abteilung Netzwerk
  Charité - Universitätsmedizin Berlin
  Campus Benjamin Franklin
  Hindenburgdamm 30 | D-12203 Berlin
  Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962
  ralf.hildebrandt@charite.de | http://www.charite.de