Has anyone gotten proxy connect to work under ssl? In my dev environment (non-ssl) everything worked perfectly. I moved to production where SSL is required and suddenly it no longer works. It takes a long time as in minutes before anything appears, and when it does it did not log in through the proxy connect I get the sign in screen. This is not a wordpress installation it is actually a rails app with vanilla forums embedded. If I disable the proxy connect things work fast, but of course users are not logged in automatically.
Thoughts?
-Dennis
0 · ·
Comments
my webserver responds to this with "Bad request".
- Spam
- Abuse
0 · Insightful Awesome LOL ·It turns out the'\x16\x03\x01' is a SSL negotiation failure. It took me a while to find out the version of cURL was incompatable with the version of OPENSSL. Identified via phpinfo();
To get around this a section of code needs to be commented out. This is in vanilla/library/core/functions.general.php and the section is within the ProxyRequest function. I commented out the section from 'if (function_exists('curl_init'))' to just prior to 'if (function_exists('fsockopen'))'.
cURL may be superior to fsock but sometimes you don't have a choice. This is just a quick hack. I'm sure somebody else can do better.
- Spam
- Abuse
0 · Insightful Awesome LOL ·I found that you have to specify the port number in the authenticate URL. Otherwise ProxyRequest in Vanilla tries to set the port to 80, which doesn't work.
So use
http://hostname.com:443/proxyconnect.php
Bad bug in Vanilla, IMO, it should look for https in the URL, if it's there set the port to 443, instead of 80.
- Spam
- Abuse
0 · Insightful Awesome LOL ·We always accept pull requests.
- Spam
- Abuse
1 · Insightful 1Awesome LOL ·