On Wed, Aug 24, 2011 at 2:14 PM, Björn Zettergren <
bjorn.zetterg...@basefarm.se> wrote:
> Hi Bill,
>
> I tried your config and i can recreate your problem. But as Eric just said
> in another mail, your browser is not using https to speak to https proxy.
> And i verified that wget speaks http when
On 08/24/2011 12:00 PM, Bill Moseley wrote:
moseley@bair ~/Documents/apache $ wget https://mail.google.com/
--2011-08-24 12:48:42-- https://mail.google.com/
Resolving localhost... 127.0.0.1, ::1, fe80::1
Connecting to localhost|127.0.0.1|:8443... connected.
Failed reading proxy response: Unknown
> And I get the same results with using wget instead of a browser (just to
> isolate that part of the problem):
> moseley@bair ~/Documents/apache $ cat ~/.wgetrc
> https_proxy = https://localhost:8443
Generally browsers don't speak https to https proxies. They use HTTP.
--
On Wed, Aug 24, 2011 at 12:47 PM, J-H Johansen wrote:
>
> I've never used Apache like this before but I suspect that you may need the
> SSLProxyEngine directive as well.
> http://httpd.apache.org/docs/2.2/mod/mod_ssl.html#sslproxyengine
>
Thanks. I was just about to update my message --- I hav
On Wed, Aug 24, 2011 at 11:16 AM, Bill Moseley wrote:
> Apache/2.2.17 (Unix) mod_ssl/2.2.17 OpenSSL/0.9.8r
> OS X 10.6.8
>
> I need help with a forward proxy setup and SSL.
>
> I have created a simple httpd.conf file with two virtual hosts, listening
> on 8080 and 8443 (accepting SSL connections)
Apache/2.2.17 (Unix) mod_ssl/2.2.17 OpenSSL/0.9.8r
OS X 10.6.8
I need help with a forward proxy setup and SSL.
I have created a simple httpd.conf file with two virtual hosts, listening on
8080 and 8443 (accepting SSL connections). I'm using a self-signed
certificate for testing. WIth this confi
