OK . The server was bombing out. Rolled it back.
> I Stand Corrected. My install *DOES* have a problem with CFLOCATION, > however it seems that the problem exists only when the file has > nothing but a CFLOCATION in it... > > Example, I have some legacy code which sits in FolderX on my site, > for the sole purpose of doing a <CFLOCATION url="../index. > cfm?Fuseaction=FolderX"> > > This no longer works after the patch (didn't catch it since its an > obscure area of the site).... I am running MX6.1 + w2K server with > all the latest patches. > > I have CFLOCATIONS Peppered throughout other areas of the site and it > works just fine. > > The following file (go.cfm) does not work: > <cflocation url="http://www.cnn.com";> > > Neither does wrapping it in <CFIF true></cfif> in case presence of > other code impacted the situation. > > HOWEVER, adding content to the page prior to the cflocation (obviously > assuming you dont cfflush) *DOES* work. The below code works: > <!--- go3.cfm ---> > TESTING > <cflocation url="http://www.cnn.com";> > > > Any ideas. Can someone ask MM to fix and post? > > -D > >> I applied to Dev, QA, and Production servers, all without incident. > > >IIS5/W2K Servers > > > >Thanks for the input... However our two environments differ enough to > make > >me think that you may not be affected by the issue I'm experiencing > anyway > > > >> I installed the JRun updater which included this patch on a dev box > today, > >no issues so far. Running a JRun cluster even too. > > > >Again, this looks like our environments are sufficiently different > for the > >issue not to surface on your environment > > > >Just as a FYI. > > > >I've just applied the patch to a second server to make sure I wasn't > going > >totally mad and I got the same issues. Any page that has a cflocation > in > >fails to force the redirect and the client seems to either sit on the > page > >it was on or returns a 'Document contains no data' error... > > > >Again I backed the patch out of the second server and everything > comes back > >to life again... > > > >Other than the fact that the first server was Windows 2003 Standard > and the > >second server was Windows 2003 Web Server, it's worth saying that > these two > >servers share and identical configuration and security policy etc. > That is > >to say all registry settings are the same, all IIS lockdown functions > are > >the same.. Everything. To all intents and purposes these boxes are > identical > >and therefore there must be something (a config setting) somewhere > that is > >causing this behaviour with the CFMX patch and IIS 6. > > > >Needless to say, its annoying that I cannot apply this patch as the > problems > >it is causing for me are far bigger than the problems that it > addresses.... > >But I am affected by the issues that it solves so I would like to get > to the > >bottom of it... > > > >If anyone has any suggestions then I'd love to hear them... > > >Paul ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:200615 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
