And it doesn't work with Cherokee 1.0.12 either.
On Dec 7, 11:36 pm, Scott Zeid <[email protected]> wrote: > Hi, > > I'm trying to proxy HTTP CONNECT requests made over HTTPS from > Cherokee 1.0.10 to an Apache2 server, and it's failing. > > In Cherokee, under Default host, I have a behavior matching Method > connect which is handled by a HTTP reverse proxy with the Information > Source "Apache", whose host is 127.0.0.1:8080. The behavior is > configured to listen over HTTPS only and use HTTP Basic authentication > with an apache2 htpasswd file. Cherokee listens on port 80 for > regular HTTP and port 444 for HTTPS. > > Apache2 listens on all interfaces port 443 for HTTPS and localhost > port 8080 for HTTP. Both allow proxy and HTTP CONNECT, and only the > HTTPS one has a password. > > To make the connection, I'm using proxytunnel 1.9.0 on Ubuntu 10.10 > i686 in the following command: > ssh -o "ProxyCommand=proxytunnel -Ep srwz.us:444 -P scottywz -d %h: > %p" <host> > > The command works when I try it directly with the Apache2 HTTPS > server, but with Cherokee HTTPS it gives me an HTTP 400 error. I've > tried it with and without authentication, and with and without HTTPS > (and I did uncheck HTTPS only) with the same results. According to > the mailing list post > athttp://lists.octality.com/pipermail/cherokee/2010-October/013659.html > Cherokee is supposed to forward the CONNECT request but it's not. > > How can I get this to work, or can Cherokee even forward CONNECT > requests, or is it a bug? > _______________________________________________ > Cherokee mailing list > [email protected]http://lists.octality.com/listinfo/cherokee _______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
