[SOLVED] FEU Login inconsistent behavior between FF and IE

[wakewatcher]

Earlier this week I was having problems trying to logout (http://forum.cmsmadesimple.org/viewtopi ... =7&t=65291 that was rectified, if not fixed, when I enabled pretty urls (I understand that was just a side effect and not a fix but I'm just describing what happened.) My browsers of choice are FF and Chrome. Today I tried signing in with an IE browser and it signs me in but you don't know it from the behaviour as it just stays on the sign in page. Doing the exact same thing with FF signs you in and brings up the signout/change settings page. Anybody seen this before and if so how do you fix it? This is a fresh (as of last Friday) installation of 1.11.4 not an upgrade.
If you care to see the behaviour you can view it here. http://screencast.com/t/nBZ2bMyv

CMSMS 1.11.4
CMSMailer 5.2.1
CMSPrinting 1.0.3
FileManager 1.4.3
MenuManager 1.8.5
ModuleManager 1.5.5
News 2.12.10
Search 1.7.7
ThemeManager 1.1.7
CGExtensions 1.31.4
FrontEndUsers 1.21.2
CustomContent 1.8.3
SelfRegistration 1.7.4
Captcha 0.4.5
TinyMCE 2.9.12
FEUMailer 0.9.4
CGCalendar 1.10.2
JM_Forum 1.0.0
CGFeedMaker 1.0.17

Edit: A user also tells me it doesn't work with Safari either.

[rotezecke]

It looks like some sort of caching problem.

i believe all pages that use FEU must not be marked as cachable. as your private content is shown in the menu you may not be able to cache any page, and/or you probably cannot cache menus either.

i'm guessing here, but i'd review page and menu caching and play with it.

[wakewatcher]

Ah. I marked it solved but forgot to mention what the problem was. One of the steps in prettifying (a technical term) urls is to add "$config['page_extension'] = '.html';" to the config.php file. I had added it but in testing (going back and forth between pretty and not so pretty) I at one point left it commented out. I didn't catch this because all worked well with the browser I generally use (FF). When later I used IE and it didn't work then at some point I stepped though the install process again and saw that I had that statement commented out. Fixed it and everything now works as expected on both flavors of browsers. I don't know why it worked in FF but in the end it is now working in general so my users are happy.