Making "Switch back to http pages when there are no matches" option enabled and making the page "node/2" to be secured, for example, I got the following:

- Trying to got to "http://mydomain/node/2", the module switch correctly to "https://mydomain/node/2".
- Trying to got to "https://mydomain/node/2", the module does a wrong switch to "http://mydomain/node/2".

I got that using Drupal 6.3 or Drupal 6.10. It is critical because if someone saves a form page that uses https in his favorites, when he gots back to it, there will be no SSL protection on the form.

Thanks in advance!

Comments

gordon’s picture

Status: Active » Postponed (maintainer needs more info)

I am not sure what you are getting at. I have tested this and I it is working as expected for me.

Anonymous’s picture

Assigned: Unassigned »

@talaco

Are you still having problems?

Please upgrade to 1.8

Best,
Paul Booker

jacksinn’s picture

I get the same problem. After enabling "Switch back to http pages when there are no matches" navigating to a page from http that I marked as secure, it works correctly like the poster's example:

- Trying to got to "http://mydomain/node/2", the module switch correctly to "https://mydomain/node/2".

However when in https and trying to navigate to a node (the same node) it switches the node to http like the poster noted:

- Trying to got to "https://mydomain/node/2", the module does a wrong switch to "http://mydomain/node/2".

Basically it is working like a toggle. When in http it switches to https and when in https it switches to http.

I'm using the stable release version 6.x-1.8

Gnanavel’s picture

I am also getting the same issue...
Can any only help.

Thanks in advance,
Vel

c3’s picture

Status: Postponed (maintainer needs more info) » Fixed

I had the same problem. I found out that you the problem comes up when there's an an empty line at the end of the secure pages list. Remove it, and the problem gets fixed.

c3’s picture

Priority: Critical » Normal
Status: Fixed » Active

Moving back to active, since I think it will be better if some code is added to trim the string of the list of pages before processing.

That way, the users (that are not aware that they should not add any extra line in the secure pages list text box) won't have this issue.

grendzy’s picture

Status: Active » Closed (duplicate)