You are viewing a plain text version of this content. The canonical link for it is here.
Posted to bugs@httpd.apache.org by bu...@apache.org on 2008/10/07 13:05:34 UTC
DO NOT REPLY [Bug 29744] CONNECT does not work over existing SSL
connection
https://issues.apache.org/bugzilla/show_bug.cgi?id=29744
Alexey Pelykh <al...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |alexey.pelykh@gmail.com
--- Comment #74 from Alexey Pelykh <al...@gmail.com> 2008-10-07 04:05:33 PST ---
Hi everyone.
I think I've found a bug, that is connected with this bug.
I have Apache vhost, that is configured to allow CONNECT to 13128 port, and
SQUID proxy server at 13128, on same server. When I try to establish tunnel
connection
External SQUID Proxy :: CONNECT home_server:443 using SSL =>
Home Apache server :: CONNECT home_server:13128 =>
Home SQUID server :: CONNECT gmail.com:443(for example, really this does not
matter what request to feed to SQUID)
it replies 400 Bad request.
But if to do same, but without SSL in tunnel, everything is OK, like
External SQUID Proxy :: CONNECT home_server:443 (SSL is disabled at my Apache
server) =>
Home Apache server :: CONNECT home_server:13128 =>
Home SQUID server :: CONNECT gmail.com:443(for example, really this does not
matter what request to feed to SQUID)
it replies 200 Connection Established
So I think it's Apache mod_proxy_connect has some bug.. Can I have some
feedback? I know that such way is rarely used (if used by someone else except
me), but this is the only solution acceptable :(
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org