|
Good to see it is fixed. It's funny how you condition
yourself around the quirks...
Darryl From: Spike [mailto:[EMAIL PROTECTED] Posted At: Tuesday, 19 August 2003 2:32 PM Posted To: CFAussie Conversation: [cfaussie] RE: what's inside CFLOCATION? (was "removing back button...") Subject: [cfaussie] RE: what's inside CFLOCATION? (was "removing back button...") It writes out the http headers so that the refresh is sent to the browser before the cookies. CFMX fixes this as does the cf_location custom tag that you can download from the MM exchange. The custom tag in the exchange just uses cfheader to write the headers in the right order. Spike Fuzion - CFAussie wrote: Does it use the META REFRESH then or ? The only reason I ask is that you cannot set cookies on a template with CFLOCATION, but I am pretty sure you can when META REFRESH is used? Darryl -----Original Message----- From: Joel Nath [mailto:[EMAIL PROTECTED]] Posted At: Tuesday, 19 August 2003 2:16 PM Posted To: CFAussie Conversation: [cfaussie] RE: what's inside CFLOCATION? (was "removing back button...") Subject: [cfaussie] RE: what's inside CFLOCATION? (was "removing back button...") Hi Brian, hate to disagree but... CFlocation is a client side redirection.. have read through this tip.. http://www.macromedia.com/cfusion/tipsubmission/tip_detail.cfm?tipid=144 when i refer to client side.. what i mean is a header is still passed back to the browser to have it request a new url.. CF server doesnt handle the redirection, its the browser that does.... cheers joel -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Knott, Brian Sent: Tuesday, 19 August 2003 2:00 To: CFAussie Mailing List Subject: [cfaussie] RE: what's inside CFLOCATION? (was "removing back button...") Not sure about ASP but <cflocation> is SERVER side redirection. The client never knows there has been a redirection. Brian Knott -----Original Message----- From: Joel Nath [mailto:[EMAIL PROTECTED]] Sent: Tuesday, 19 August 2003 1:51 PM To: CFAussie Mailing List Subject: [cfaussie] RE: what's inside CFLOCATION? (was "removing back button...") Hi Barry, try the following... <CFSCRIPT> request.myvar = "barry"; getPageContext().forward("yourtemplate"); </CFSCRIPT> any CF variables created on the starting page can be made available on the page to which control is forwarded. The only requirement is that they are only made available if they are placed in the REQUEST scope. Then they are available in the called page also in the REQUEST scope. also if i am not wrong response.redirect works slightly differently to cflocation but both do client side re-directions cheers joel -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Beattie, Barry Sent: Tuesday, 19 August 2003 10:15 To: CFAussie Mailing List Subject: [cfaussie] what's inside CFLOCATION? (was "removing back button...") Hi All just wanted to check: is CFLOCATION just "Error 302 page Moved Temporarily. new url=''" which is equiv to ASP's response.redirect, yes? my main question is: is there a CF version of ASP's server.transfer (which works differently)? <quote src=""http://www.devguru.com">www.devguru.com"> ***useage: Server.Transfer(Path) *** The Transfer method allows you to transfer from inside one ASP page to another ASP page. All of the state information that has been created for the first (calling) ASP page will be transferred to the second (called) ASP page. This transfered information includes all objects and variables that have been given a value in an Application or Session scope, and all items in the Request collections. For example, the second ASP page will have the same SessionID as the first ASP page. When the second (called) ASP page completes its tasks, you do NOT return to the first (calling) ASP page. </quote> thanx barry.b -----Original Message----- From: Beattie, Barry [mailto:[EMAIL PROTECTED]] Sent: Tuesday, 19 August 2003 9:56 AM To: CFAussie Mailing List Subject: [cfaussie] Re: removing back button... this is to stop multi form submits, yes? one handy trick we used to do was to response.redirect (Ooops! CFLOCATION) the browser to another page after the form had been processed. sure they could go back and back but you could do things like check if the http_referer was or was not the page with the form and deal with accordingly. cheers barry.b -----Original Message----- From: Gary Menzel [mailto:[EMAIL PROTECTED]] Sent: Tuesday, 19 August 2003 9:10 AM To: CFAussie Mailing List Subject: [cfaussie] Re: removing back button... -- Stephen Milligan Consultant for hire http://www.spike.org.uk--- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] MX Downunder AsiaPac DevCon - http://mxdu.com/ --- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] MX Downunder AsiaPac DevCon - http://mxdu.com/ |
- [cfaussie] RE: what's inside CFLOCATION? (was "remo... Joel Nath
- [cfaussie] RE: what's inside CFLOCATION? (was "... Fuzion - CFAussie
- [cfaussie] RE: what's inside CFLOCATION? (was "... Fuzion - CFAussie
- [cfaussie] RE: what's inside CFLOCATION? (was "... Mark Stanton
- [cfaussie] RE: what's inside CFLOCATION? (was "... Fuzion - CFAussie
