In my case I have Drupal running behind a corporate firewall and the only way out is via a proxy.

There's a couple of really old open issues #924498: Proxy https support for drupal_http_request() [#2291641] and this closed related one from 10 years ago #7881: Add support to drupal_http_request() for proxy servers (http not https) (node 7881 wow!)

In this case Drupal will throw an exception with 'Error 400 bad request' or 'Error: 501, Not Implemented' which ever the proxy decides to send, Drupal 7 simply does not support HTTPS via Proxy (as well as HTTP/1.1 either but that hopefully wont be an issue)

I've had some success with https://www.drupal.org/project/chr

So the feature request here is - is it worthwhile to add a warning message if you have a https proxy enabled?

Comments

Devin Carlson’s picture

Devin Carlson CreditAttribution: Devin Carlson commented
Category: Feature request » Support request
Status: Active » Closed (won't fix)

This should be handled by Drupal core instead of adding a warning to every module which calls drupal_http_request().