> > Plus its always worth putting a cfabort after your > > cflocation, just to be sure that CF doesn't even bother > > trying to process anything after the cflocation. > > I tried that and it didn't change anything. > > Also, it seems very silly to have to do that. Surely it would be a "bug" if > any code was run after the cflocation. > Ummm... I can't remember if cflocation is browser or client side redirection..... (I think it used to be client side, not sure now)
If its client side, then strictly speaking no, because CF would still have to process the entire page before pushing the page to the web server and then the client, unless you tell it otherwise. If its server side, then I guess yes it would be, but old habits die hard. ;o) What does your form variable actually contain? Stephen -- ** Archive: http://www.mail-archive.com/dev%40lists.cfdeveloper.co.uk/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] For human help, e-mail: [EMAIL PROTECTED]
