Would this be tacky?

I have 3-4 pages that handle some processes of adding data to the db. I need to be able to keep track of a referring page, so once the user is finished with this process, they'll be routed back to their starting point. At first, I started creating URL variables, passing them from one page to

Re: Would this be tacky?

I'm thinking about creating a SESSIOn variable to handle it. The user clicks the link to handle the processes, I set the session variable to the start page. When the user is finished, I check to see if that session var exists. if it does, send them back to the starting point. This is

Re: Would this be tacky?

I agree, Don't be afraid of sesion vars. I have apps that drop huge structs and arrays into each users session. This is the way to go. -- Alan Rother Adobe Certified Advanced ColdFusion MX 7 Developer Manager, Phoenix Cold Fusion User Group, AZCFUG.org

Re: Would this be tacky?

Thanks guys! It's done. :) Will ~| Create robust enterprise, web RIAs. Upgrade integrate Adobe Coldfusion MX7 with Flex 2 http://www.adobe.com/products/coldfusion/flex2/?sdid=RVJP Archive:

Re: Would this be tacky?

How about using CGI.HTTP_REFERRER? Will Tomlinson wrote: Thanks guys! It's done. :) Will ~| Deploy Web Applications Quickly across the enterprise with ColdFusion MX7 Flex 2 Free Trial

Re: Would this be tacky?

On 7/3/07, Christopher Jordan [EMAIL PROTECTED] wrote: How about using CGI.HTTP_REFERRER? This is getting to be less and less useful. Many of the internet security software packages (Norton, ZoneAlarm, etc.) scrub the referrer info from the user's http request as part of the privacy features.

Re: Would this be tacky?

Yeah, but isn't this guy talking about needing the referring page on a system that he controls? My understanding was that he needed the referrer from page to page *within his own app*. Chris Doug Bezona wrote: On 7/3/07, Christopher Jordan [EMAIL PROTECTED] wrote: How about using

Re: Would this be tacky?

Will is talking about making the value persist across multiple page loads. The cg.http_referer would be incorrect at the final processing point. He needs to lock in a value as soon as the user starts a multi step process. On 7/3/07, Christopher Jordan [EMAIL PROTECTED] wrote: Yeah, but isn't

Re: Would this be tacky?

Yeah, but isn't this guy talking about needing the referring page on a system that he controls? My understanding was that he needed the referrer from page to page *within his own app*. I don't know if that would work for him anyway though...he wants to hold an originating page in memory over

Re: Would this be tacky?

But the referrer is supplied by the browser, so he has no control at all whether that information will be available. If he knows for sure none of his users have any software that might strip the information, he would be fine, but beyond that, it's just not reliable. On 7/3/07, Christopher Jordan

Re: Would this be tacky?

Yeah, the CGI.http_referer doesn't quite work like I need. I just ended up storing the originating page in SESSION, so it's readily available to any template that's involved in this process. Seems to work fine so far. Thanks, Will

Re: Would this be tacky?

Oh, I see. I didn't realize that's what you wanted. Oh well. Sorry. Chris Will Tomlinson wrote: Yeah, the CGI.http_referer doesn't quite work like I need. I just ended up storing the originating page in SESSION, so it's readily available to any template that's involved in this process.