Support for URL aliases

I wrote a quick solution for this. In the securepages.module file (I actually added this to drupal 5),
in the securepages_init function, I added 2 lines, which fixed the problem:

function securepages_init() {
...
$path = $_GET['q'];
$page_match = securepages_match($path);
// PATCH:
if (!$page_match)
$page_match = securepages_match(request_uri());
...
}

This checks the external url if the internal url failed in the match.
I am new to Drupal, so I don't know how to write patches yet, I will post one as soon as I can.

Eek, sorry, made a mistake.
You need to remove the heading "/" character first.

$page_match = securepages_match(ltrim(request_uri(), "/"));

I found this working better when you have your drupal installation not at the host's root:

$page_match = securepages_match($path);

if (!$page_match){
$page_match = securepages_match(drupal_get_path_alias($path));
}

I'm currently testing on the server, so the URL is http://example.com/test/, thus request_uri() still contains the 'test' part in my example.

Not sure how this works if there's various aliases to a node.

Shouldn't this feature be part of the module?

I found this working better when you have your drupal installation not at the host's root:

$page_match = securepages_match($path);

if (!$page_match){
$page_match = securepages_match(drupal_get_path_alias($path));
}

I'm currently testing on the server, so the URL is http://example.com/test/, thus request_uri() still contains the 'test' part in my example.

Not sure how this works if there's various aliases to a node.

Shouldn't this feature be part of the module?

this:

if (!$page_match){
$page_match = securepages_match(drupal_get_path_alias($path));
}

seemed to work at the beginning, but then I found out that the call to drupal_get_path_alias() throws an error sometimes that it's not available.

I'm using a different approach now. I'm back to the original settings in the secure_pages module and added this line to my settings.php:

ini_set('session.cookie_secure', 1);

The login is secure and the session will be valid for https only with this setting. As soon as the users tries to request a page using http she gets logged out.

It's not 100% what I wanted, but now I can be sure that the pages that only some authenticated users are allowed to see are always encrypted.

automatically closed - The 4.7 branch is no longer supported. If this issue is present in a currently supported version, please change the version field and re-open. Thanks!