Something to consider…
Depending on your server, you may want to utilize a URL rewrite so you are always loading the same domain. Easy to do and it solves a lot of headaches. Also better for SEO, if you are into that sort of stuff. The rewrites at the server level does it’s magic before you even hit the first .taf file. This way, the only time you would need to send a userreference is when switching the domain. Examples would be going from… http://thisdomain.com to https://thisdomain.com Or… http://thisdomain.com to http://thatdomain.com Regards, John Muldoon Corporate Incentives 3416 Nicollet Ave S Minneapolis, MN 55408-4552 612.822.2222 <mailto:[email protected]> [email protected] cid:875001213@05112012-110E <http://cipromo.com/> http://cipromo.com From: Bishop Weiss [mailto:[email protected]] Sent: Wednesday, December 18, 2013 1:37 PM To: [email protected] Subject: Re: TeraScript-Talk: One more Time John, Thank you so much. I think that was it. So I force any request go to the URL that doesn't have www. in the front. So far it's working. Thanks so much. Mark Weiss On Dec 18, 2013, at 6:16 AM, John Muldoon <[email protected]> wrote: Hi Bishop, Are you using absolute links? In other words, going to a www page from a non-www page or the other way around? We have had to make sure that we are always in the same domain/subdomain in order for the stars to align. On most of our sites, we do URL rewrites in order for users to all use the same links. In other words, going to a login page as http://www.loginpage.taf and clicking a link that goes to http://logindone.taf will cause problems like this. A workaround would be to pass the <@userreferrence>. -----Original Message----- From: Bishop Weiss [mailto:[email protected]] Sent: Tuesday, December 17, 2013 6:18 PM To: [email protected] Subject: TeraScript-Talk: One more Time Robert. Are user variables somehow tied to the taf that creates them? I have time to track this problem down now that school is out. I have a login taf that lands on a simple HTML page when log in is good. As part of the log in, I assign user variables and one is to verify that log in has occurred. When I click on a link on the landing page, that goes to another taf, I check for the variable and nearly 100% of the time I am logged out. I log in a second time, and from that point forward during my session, I can go anywhere and not get bumped off. However, when variables expire, that same routine happens again. We have to log in twice, to make login happen. Most users are aware of this, and go along with it, but it is so rookie on my end of things. Witango 5.5 Mac os X server 10.4.11 Connected to MySql. I think you explained it to me once before, but if you could help me figure out why this happens? Do I need to set a cookie that expires, and check for that instead. I can. But before I do all of that changing, I wanted an expert opinion. Thanks Mark ---------------------------------------- To unsubscribe from this list, please send an email to [email protected] with "unsubscribe terascript-talk" in the body. ---------------------------------------- To unsubscribe from this list, please send an email to [email protected] with "unsubscribe terascript-talk" in the body. _____ To unsubscribe from this list, please send an email to [email protected] with "unsubscribe terascript-talk" in the body. ---------------------------------------- To unsubscribe from this list, please send an email to [email protected] with "unsubscribe terascript-talk" in the body.
<<image001.gif>>
