> Indeed easy. But wrong :) > > Although your description of what happens is quite > accurate for the current browsers, you are depending > on features that are not compliant with the HTTP/1.1 > specification. > > ... > > A redirected POST should result in a POST for the next > page, not a GET, and a POST is never allowed to be > without user intervention. If you use cflocation in > response to a POST from a HTTP/1.1 compliant browser > the user will get a popup asking him if he wants to be > redirected, which is usually not desired behaviour.
I'll be happy to leave "how it should be" to you; I'm content to describe how it is. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ voice: (202) 797-5496 fax: (202) 797-5444 ______________________________________________________________________ Get the mailserver that powers this list at http://www.coolfusion.com FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
