Ambiguous behavior of nginx / ruby ​​/ thin server setup session variables

Web server setup: nginx / thin / ruby-sinatra

I am using a session object from ruby ​​to store various information and return to the path

session[:username] = 'username' session[:token] = 'token' session[:error] = '' session[:return_to] = '/start_page' 

tasks1:

On my server, if the client is IE, all information in the session object is lost when I reload the page. Firefox and Chrome are working fine.

If I take the code of the save web page and put it on another server with the same setting, I have no problem at all. All 3 browsers (the same client) work well and remember sessions.

What could interfere with the installation? Why only IE?

tasks2:

On my server, the [: session_id] session is not initialized until I set some variable to the session, but if I run the same code on another server, the [: session_id] session is available with the very first access.

Why is there a different behavior for completely identical settings?

+4
source share
1 answer

This seems to be a bug with Sinatra 1.3.1, see comments on the issue of resolution

0
source

All Articles