I figured it out! It was caching pages. I found a post to add this in the <head> element:
<META HTTP-EQUIV="Pragma" CONTENT="no-cache"> <META HTTP-EQUIV="Expires" CONTENT="-1"> and everything looks to be working. Thanks for your input. On Oct 16, 2:59 pm, gwgeller <[EMAIL PROTECTED]> wrote: > Shandy, > I've just spent some time looking through the production log. I > noticed the IE7 requests were sometimes erroring out because of > InvalidAuthenticityToken errors. But I know this happens when cookies > are turned off so if the IE7 sessions aren't working right this error > will probably exist. But just in case I disabled the AuthenticityToken > and the problems are still there. > > Looking more into the log I see that not every IE7 request is being > logged, so the request must not actually be taking place. Almost like > IE7 is caching or something to that nature. If I refresh each page it > seems like things work like normal. Any ideas? I'm going to start > looking into caching and stuff like that. > > On Oct 16, 2:14 pm, Shandy Nantz <[EMAIL PROTECTED]> > wrote: > > > In IE7 i got 500 errors. Could it be that there might be puts statements > > in your controller? I have found that that will reek havok on the app > > sitting on our server and will usually give a 500 error. Also, you say > > the session persists, are you resetting the session variable somewhere, > > like when you logout? Are there any useful hints in the loggs? > > > -S > > -- > > Posted viahttp://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
