Re: [SM-USERS] Still problems with 1.4.19 and "you must be logged in" error

Please quote messages you are replying to.  Unquoted text that belongs
to someone else should not appear in your message.

> We are experiencing the same exact type problems as mentioned above by
> Rafael and are also running squirrelmail 1.4.19 on RHEL 5.3 with Apache
> 2.2.11 and PHP 5.2.5. I have tried commenting the whole IF statement around
> line 82 in src/redirect.php and that did not work for us. I am using IE 7
> to test.
>
> What I am seeing is intermittent and varies as such:
> 1.  Sometimes when browsing to src/login.php I am redirected to the login
> error page instead.
> 2.  When browsing to src/login.php and not redirected to the login page and
> successfully log in, either both frames or one of the frames will be blank
> while the other correctly displays the web content.

Please provide error information for the blank frames.  You should
find how to diagnose blank pages if you search for it.  Hint: check
your logs.

> 3. When browsing to src/login.php and not redirected to the login page and
> successfully login, either both frames or one of the frames will display
> webpage cannot be displayed while the other correctly displays the web
> content.
> 4. Clicking on IE's refresh sometimes successfully refreshes the faulted
> frame and other times takes you to the login error page.
> 5. After logging in with both frames working and just leaving the browser
> sitting there with Inbox messages displayed, the left pane either goes
> blank or displays webpage cannot be displayed. I think it must be occurring
> during an auto refresh of the folders pane (as set in the folder options) .
>
> When I  simply reconfigure httpd.conf to point to webmail-1.4.17 vice
> webmail-1.4.19 and restart the httpd service all of the above problems go
> away.

So many problems sound fishy to me, but ultimately, it's something you
have to help us reproduce or we can only take guesses.  Please try
other browsers and please provide exact details about the cookies that
are in the browser when things go bad.  Exact detailed steps to
reproduce the issue are best.

> I have not seen a response back to Rafael's email above yet and was
> wondering what the status of this is and if there is something that can be
> done to correct this. I am anxious to go back to 1.4.19 because of all of
> the security fixes contained in 1.4.18 including the very important fix
> regarding remote execution of server side code.

-- 
Paul Lesniewski
SquirrelMail Team
Please support Open Source Software by donating to SquirrelMail!
http://squirrelmail.org/donations.php

------------------------------------------------------------------------------
-----
squirrelmail-devel mailing list
Posting guidelines: http://squirrelmail.org/postingguidelines
List address: [email protected]
List archives: http://news.gmane.org/gmane.mail.squirrelmail.devel
List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-devel