that's right. cflocation is really a clientSide re-direct (error 302 page has moved).
I haven't tried it but using a server-side "move" getPageContext().forward(url) might hang on to request scope - it certainly keeps FORM vars! just an idea barry.b -----Original Message----- From: 'Ayudh Nagara' [mailto:[EMAIL PROTECTED] Sent: Wednesday, 5 May 2004 10:41 AM To: CFAussie Mailing List Subject: [cfaussie] Request scope Simple back-to-basics question. According to the CF documentation Request scope is: "Used to hold data that must be available for the duration of one HTTP request..." Question is, if we use CFLOCATION in one page to load another page, is it counted as the same or a separate HTTP request? Because it seems that Request scoped variables are lost in the process. Regards: Ayudh +----------------------------------------------------------------+ | SOAP is the glue! Hook up your server directly to your bank. | | Connect to VeriPay xServ, the Australian Payments Web Service. | | Reliable, Secure, FAST: http://www.xilo.com/xserv | +----------------------------------------------------------------+ --- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] MXDU2004 + Macromedia DevCon AsiaPac + Sydney, Australia http://www.mxdu.com/ + 24-25 February, 2004 --- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] MXDU2004 + Macromedia DevCon AsiaPac + Sydney, Australia http://www.mxdu.com/ + 24-25 February, 2004
