https://forum.navigraph.com
please note https
and therefore you need to enable cookie secure. Also, you need to put a redirect in your .htaccess file to direct everything to https.Code: Select all
#Rewrite everything to https
RewriteEngine On
RewriteCond %{HTTPS} !=on
RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]
RewriteEngine on
when you edit .htaccess.Maybe I don't understand this part in cookie settings:
So in my configuration AWS Load Balancer works with web server via http. It works like this:If your server is running via SSL set this to enabled else leave as disabled. Having this enabled and not running via SSL will result in server errors during redirects.
Persistence
An important issue when operating a load-balanced service is how to handle information that must be kept across the multiple requests in a user's session. If this information is stored locally on one backend server, then subsequent requests going to different backend servers would not be able to find it. This might be cached information that can be recomputed, in which case load-balancing a request to a different backend server just introduces a performance issue.[7]
Ideally the cluster of servers behind the load balancer should be session-aware, so that if a client connects to any backend server at any time the user experience is unaffected. This is usually achieved with a shared database or an in-memory session database, for example Memcached.
One basic solution to the session data issue is to send all requests in a user session consistently to the same backend server. This is known as persistence or stickiness. A significant downside to this technique is its lack of automatic failover: if a backend server goes down, its per-session information becomes inaccessible, and any sessions depending on it are lost. The same problem is usually relevant to central database servers; even if web servers are "stateless" and not "sticky", the central database is (see below).
To "blame" the LoadBalancer is the very first idea I had to be honest. In the end, we could reproduce the issue with only web-server. I mean there is the only web-server "after" the load balancer and there is no any DB/cache to share between web-servers. My plan is to exclude the LoadBalancer even though I am almost sure this is not the reason - just to exclude it as the cause. Any other ideas? Any debug/log on client side with browser dev tools? Thank you
Registration is closed on the forum so answer "Yes" is wrong but "No" is also not true - a bit confusing, sorry about that. Anyway I created test account which you could use to reproduce: phpbbtestlogout/phpbbtestlogout1 - this is the test credentials. As I said before to reproduce is not so easy and I still don't know to do it step by step - and this is my main problem. Thank you
.forum.navigraph.com
. It works in some cases.