There is neither a documentation available, nor any requirement displayed in the module list. So I expect that the module does what it's described to do: Right after it's installed and activated, it should redirect any user who is authenticated to the https:// version of the site if it's http:// .
But this doesn't happen; it looks as if the module doesn't do anything at all.
I use it with Drupal 7.18 and only the following 3rd party modules installed:
Administration menu
reCAPTCHA
CAPTCHA
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | auth_ssl_redirect_cookie_missing-1882082-2.patch | 1.51 KB | Nephele |
Comments
Comment #1
coltraneAfter you authenticate can you check on the cookies stored by your browser? Confirm if you have the AUTHSSL cookie or not.
Comment #2
Nephele commentedI experienced the same problem with the module on my test site. I logged in after enabling the module then checked my cookies and there was no AUTHSSL cookie.
In my case at least the problem is that setcookie() was using an invalid domain. My site's URL is "site.local" (because it's my local MAMP-hosted copy of the site), which resulted in auth_ssl_redirect trying to calling setcookie() with a domain of ".local". Based on the PHP documentation and the comments in drupal_settings_initialize(), the same problem probably occurs for anyone using "localhost" or a numeric IP ("127.0.0.1").
In the attached patch, I've adapted the valid-domain test used by drupal_settings_initialize(). The patch fixes the problem for me: after logging in I have a AUTHSSL cookie, and http pages are redirected to https.
(I also took the liberty of tweaking some of code earlier in the function, because having this module alter a global variable, namely $cookie_domain, seems unnecessary and potentially problematic).