Hi, the Secure By Role module is exactly what I need for my current site ! To my mind it's the best way to secure the content editing...
Here is the bug description : when the module is installed and activated, it causes an infinite loop to the same page.

Hope this problem should be fixed asap...

PS : Many thanks to the author and his README.TXT, it saved me cause the site was totally unavailable, and I found the solution to quickly disable the module.

Comments

Garrett Albright’s picture

Assigned: fchak » Unassigned
Status: Needs work » Active

Did you enter a path in the "Secure server URL" field which is not a path to a secure server (starts with http:// instead of https://)?

fchak’s picture

Hi Garrett,

I tried these values :
- http://xxxxxxx.com --> Infinite loop
- https://xxxxxxx.com --> idem
- [no path] --> idem

I precise that the SSL certificate is rightly configured cause the https://xxxxx.com works in a browser...

Thanks in advance.

Garrett Albright’s picture

Yes, entering in a path with an http:// prefix will cause problems, because the code will notice the user isn't using HTTPS, so they'll redirect the user to the server specified by the "Secure server URL" value, but that's an HTTP connection, so the code will notice the user isn't using HTTPS, so they'll redirect the user to the server specified by the "Secure server URL" value, but that's an HTTP connection, so…

What do you mean by "idem?"

fchak’s picture

Garrett,
thanks for your help.

Sorry for "idem", this french word means "ditto" in English, or "same as before" ;)

In the end, on my current website, I installed securepages module and after some changes in the securepages.module file, it has worked.
Many thanks again, I'll follow the progress of this recent module (secure by role) because it should be very useful.
Bye.

szczym’s picture

I confirm the bug, the loop is crashing database on my server (!) with default (empty) value in "Secure server URL:" or with full https url.

My website works on https.

szczym’s picture

I found similar issue in secure pages http://drupal.org/node/420712 maybe its related ?

szczym’s picture

Temporary solution is to use module Securepages with the patch from hire: http://drupal.org/node/1134238#comment-4501526

Garrett Albright’s picture

Sorry, but I haven't used or worked on this module in years… I think it's time to find another maintainer to take it over. Anyone interested?