I'm not sure if this is the right forum, but here is the situation:

We have two identical virtual servers (both with the environment set
to development) that we deploy to with Cap (2.5.0) using multistage
(1.2.1). At the moment, we are just using Apache (2.2.8), and will be
setting up the mongrels in a week or so. It' a new application, with a
push the just get the 1st version available for internal viewing and
comments.

Both servers work quite well using Firefox, but when we access the
site with IE (version 7), one of the servers works just fine through
the log-in process, and the 2nd server refuses to let the user log
in.

We are using session IDs stored on the server, and in troubleshooting
this, have found that the session IDs for the Firefox users and the IE
users for the good system stay consistent as they move around the
site, as we would expect. However, we have found that the IE users
going to the "bad" system have their session ID change constantly when
they go to different pages or even refresh the same page.

We have one controller dedicated for log-in, which will then pass the
user over to their homepage.  On the bad system, after the user enters
the log-in information, control passes to the next controller, which
seems to start processing code when it bounces back with the message:
"Filter chain halted as [:authorize] rendered_or_redirected." This
pointed us to the session IDs.

Both systems have the same version of code deployed to them (multiple
times), the apache.conf files, the .htaccess and dispatch are
identical. We have looked at file permissions, and have gone over the
code with a fine tooth comb.

Any assistance to get is looking in the right direction would be
greatly appreciated.

Thanks,

    Salvin

--~--~---------~--~----~------------~-------~--~----~
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/capistrano
-~----------~----~----~----~------~----~------~--~---

Reply via email to