Login prompt LOOP, how to beak the cycle??

[SteelDragon]

Ok, here is my problem, I have an application.cfm, and I set application variables, everything is cookie driven,on my testbed the site works great, when I move it to a simulated production server (our back-up site) the site goes into a login loop when you try to log in. The CFM pages are still located on the same box, they are just contained in a frame on the back-up server's pages. The strangest part is if I log into my testbed (same exact page) before I log into the back-up the site works fine for all users. I don't quite understand how the same exact pages can act differently when contained in a frame (n=on the Back-up production box), as opposed to when they are not(the tesbed accessed directly).

Very Purplexed
SteelDragon

 

[strantheman]

So you're using application variables along with cookies.. why do you need both?

Your frameset is on Box A.

http://boxA/index.html.

One of those frame's target's is on Box B, maybe

http://boxB/login.cfm.

This is an HTTP request to a different web site, with its own application settings. Your frame set file is located on a server with its own application settings as well.. there could be a conflict here.

Is the login.cfm form action relative or abolute? Can you be sure which application.cfm is being accessed by the form action?

Id need some more info before speculating, let me know if you have more.

 

[SteelDragon]

strantheman,

Box A is all html, Box B is the CFM box, there is only 1 application.cfm over the entire app. I have a login form that is action driven, it quearies a SQL DB, pulls user information, compares it to what was entered in the form, and validates the user, then passing them to a page where they can select which of two secured sections they want to enter. All of these (CFM) pages reside on server B in the same directory, and Server A puts them in the main frame of an html site. I removed the cookies, as I have found the other part of the site (ASP) no longer requires them (I'm not responsible for that part). But I still get the looping. Again, if I go to the CF pages directly on the CF box, no problem, only when accessed through the frames do I get into this loop. BUT, If I access the CF box FIRST and then go in to the site from the frames box (Box A) it works for a few hours until it seems to "reset", and then I have to go into the CF Box ( Box B ) and login again, so that the normal users accessing Box A can get in. Make any sense?

Thanks,
SteelDragon

 

[strantheman]

If I saw your application.cfm I might have more ideas, but sounds like your session management is operating fine.. its timing out and you're having to relog in, which isn't really a fault. And, its tracking state for multiple users. I would have used cookies instead of cfapplication but they are simply two different methods of setting state variables.

Is there anything in your application.cfm with conditionals about where to redirect if something happens... or maybe in your action page? Tell me about every existance of <CFLOCATION, action=, and if you're using some sort of fusebox approach any <CFINCLUDE .

Beyond all that im still with you .. thats crazy.