>If you do a server-side redirect the browser won't put B in >history, only A and C. If you use a META tag or JS's window.location >you'll get B in history, but not with server-side.
Possibly getting into the realms of pedantry, because you're ultimately correct, but "server-side" is a bit inaccurate. cflocation performs a HTTP-level redirect, which still "touches" the client. A "true" server-side only redirect is one that is entirely transparent to the client (such as mod_proxy might do), and would still need "protection" from unwanted repeat-loading issues. I may well have gone and confused some people more now, so in an attempt to summarise/clarify... - Server-side redirect = only occurs on the web server, client is unaware it happens. - HTTP redirect = cflocation (or cfheader) = occurs at low-level on client, user probably unaware (unless they watch the traffic). - Meta redirect = occurs in browser via HTML, usually after defined delay. - JavaScript redirect = occurs in browser via JavaScript, as soon as location.href (or similar) is executed. The first two will not cause history entries, the last two will. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Adobe® ColdFusion® 8 software 8 is the most important and dramatic release to date Get the Free Trial http://ad.doubleclick.net/clk;207172674;29440083;f Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:316526 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
