I am protecting a php page using the approach described here in the Amember : http://www.amember.com/docs/Content/PHPScripts It works well, except once user is logged in, it launches the content page as an https page (note the s), which is causing some problems. Is there a way with this amember protection method to leave https active for the login process, but then use http (non secure) access for all (or some) of my content pages? Thanks for thoughts on this! PS, I saw the forum post with a similar issue: https://www.amember.com/forum/threa...ept-for-a-url-then-switch-back-to-http.16694/ but saw no final working outcome. Is this the solution? Other simpler ways? Thanks.
How do you link to your protected content initially? Through http or https? aMember will redirect to the same scheme after login, so for example if user went to http://example.com/protected_file.php He will be redirected to https://www.example.com/amember/login.php and then after login will be redirected to http://example.com/protected_file.php But if user went to https://example.com/protected_file.php he will be redirected to https page after login.
Thanks, but that is not my experience. The initial link is http, then at login it switches to https, and then it *stays* at https when it returns to the page after login. To confirm this, I tried just copying the http link into the browser, but got same result: it switched to https after login and stayed at https. Any other thoughts? Appreciate it!