Can you explain briefly about your problem with secure-pages modules? In this same scenario, I am using EngineX for SSL termination and it will reverse proxy to Apache Server. A Varnish server play nice with HTTP Protocol, EngineX will take care of HTTPS protocol.
This was so long ago I've forgotten some of the details, but here's a short version based on what I remember.
Some browser (in this case, mostly some older versions of IE) have limitations of how they can do an SSL "handshake". For those versions, it is NOT sufficient to run the PHP app server on HTTP and let the AWS ELB handle HTTPS. While this works for most browsers, it failed for some, at least in 2012.
The fix was to make sure the app server itself could handle SSL, using the same certificate as the ELB. Drupal was set up to "speak" both HTTP and HTTPS, based upon the server variables passed to it. This made sure that the HTTP ==> HTTPS transition worked correctly on all the browsers we needed to handle.
This was a very difficult issue to debug, since it's very specific to particular browser versions. But it was a serious problem, since we were seeing sizable numbers of people who could not use our application. That the problem was occurring due to different implementations of the SSL protocol itself didn't help either.
D7 reached its EOL back in January 2025, and there is no active release for D7 for this module anymore.
Development or support is not planned for D7. All D7-related issues are marked as outdated in a bunch.
The 2026 Drupal Business Survey is open. Your response will help shape the future of the Drupal business ecosystem.
Comments
Comment #1
subbiah.drupalgeeks commentedHello Torenware
Can you explain briefly about your problem with secure-pages modules? In this same scenario, I am using EngineX for SSL termination and it will reverse proxy to Apache Server. A Varnish server play nice with HTTP Protocol, EngineX will take care of HTTPS protocol.
Subbiah S | Linux Administrator
Comment #2
zied.ellouze commentedDid you find a solution?
Comment #3
Torenware commentedThis was so long ago I've forgotten some of the details, but here's a short version based on what I remember.
Some browser (in this case, mostly some older versions of IE) have limitations of how they can do an SSL "handshake". For those versions, it is NOT sufficient to run the PHP app server on HTTP and let the AWS ELB handle HTTPS. While this works for most browsers, it failed for some, at least in 2012.
The fix was to make sure the app server itself could handle SSL, using the same certificate as the ELB. Drupal was set up to "speak" both HTTP and HTTPS, based upon the server variables passed to it. This made sure that the HTTP ==> HTTPS transition worked correctly on all the browsers we needed to handle.
This was a very difficult issue to debug, since it's very specific to particular browser versions. But it was a serious problem, since we were seeing sizable numbers of people who could not use our application. That the problem was occurring due to different implementations of the SSL protocol itself didn't help either.
Comment #4
astonvictor commentedD7 reached its EOL back in January 2025, and there is no active release for D7 for this module anymore.
Development or support is not planned for D7. All D7-related issues are marked as outdated in a bunch.