>>> Jesse Vincent <[EMAIL PROTECTED]> 08/15/06 05:25PM >>> On Tue, Aug 15, 2006 at 04:58:07PM -0400, Tony Graziano wrote: <snip> So. Is this a 3.6.1 with no local customizations whatsoever that's breaking? If so, the right next step is to turn on cookie notification in your browser and see if RT is sending a new cookie right before each forced relogin attempt. Also, it's worth stopping apache, clearing out rt's var/mason/obj directory, and starting apache again. It's possible for some things to get cached across server restarts. <snip> Yes, it is setting a cookie at the login again. What gives? Usually it is when a ticket is being reolved (with or without response to requestors, or when manually creating a new ticket and "saving it". All the input is saved, and it takes you right back to the same ticket.I did stop apache and clean the obj directory, and turned on firefox to prompt for all cookies. When i got kicked out to the login screen, it prompted me to set a cookie when I hit "Login". ------------------------ For LAN Support: http://www.myitdepartment.net/index.php?option=com_content&task=view&id=13&Itemid=29
For Internet Support: http://www.cavalierbroadband.com/index.php?option=com_content&task=view&id=41&Itemid=30 _______________________________________________ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: [EMAIL PROTECTED] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
