So is the only way around this to do a CFHEADER instead of a CFLOCATION? The solution I ended up going with was replacing my CFLocation with <CFHEADER Name="Refresh" Value="0; URL=Index.cfm?FuseAction=Display">
-----Original Message----- From: Nick McClure [mailto:[EMAIL PROTECTED]] Sent: Wednesday, November 21, 2001 11:54 AM To: CF-Talk Subject: Re: Netscape Object Moved problem It is because of what CFLocation does. Netscape follows the standard to a T and IE does not. CFLocation issues a response code of 403 Object Moved. The browser is supposed to resend the original request to the new page. Netscape resends all of you form data to the new page. IE Does not do this. In all actuality Netscape is working correctly IE is not. At 11:47 AM 11/21/2001 -0500, you wrote: >Hey all, > >I have a site that's using a bastardized version of Fusebox, but follows the >general method of having a central "fusebox" page and multiple fuseactions >in a switch statement. Everything works fine in IE, but when I bring up >index.cfm?fuseaction=display more than once in Netscape (versions 4.73 and >4.76) I consistently get an "Object Moved, This document may be found here" >error for every page I try to bring up. When I click on the link to where >the object has moved to, it works fine. > >Any ideas? I've tried putting in meta content-type, expires, and pragma >no-cache tags and still no dice. I have a sneaking suspicion that this has >to do with CFLOCATION and am going to play around with headers now... > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 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
