It was completely random in fact. I don't know the exact details but it seemed to be linked to sessions; Ie. everything would work well until a certain point, then after that point relocations would not work for the rest of the session.
It was possible to have two computers accessing the site, one would work, one wouldn't. After a few or a lot of clicks, both computers would stop working. I guess I left that last part out. It seemed at first glance to be an issue specific to one computer but after a while it became apparent on all of them. It was apparent only in Internet Explorer, which would show the relocated URL in the address bar, with the truncated code from the previous page in the browser window. Firefox "seemed to" behave normally. It was just one server that was causing the problem. We've been running on win2000 for years and this is our first 2003 server. We also upgraded to SQL 2005 and the performance difference is huge over SQL 7. Just had a few of these niggling "architectural" bugs in the process :( All is good now, thanks Joel -----Original Message----- From: cfaussie@googlegroups.com [mailto:[EMAIL PROTECTED] Behalf Of Charlie Arehart Sent: Thursday, 27 July 2006 11:16 AM To: cfaussie@googlegroups.com Subject: [cfaussie] Re: CFLOCATION Issue Good tip to share. But shouldn't the two different computers have experienced the same thing if it was a server problem? Or are you saying that there were two different servers being tested against? /charlie http://www.carehart.org/blog/client/ -----Original Message----- From: cfaussie@googlegroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Joel Cass Sent: Wednesday, July 26, 2006 7:12 PM To: cfaussie@googlegroups.com Subject: [cfaussie] Re: CFLOCATION Issue Hi I found the issue, it was jrun updater 6: http://www.adobe.com/cfusion/knowledgebase/index.cfm?id=5c9389c8 Jrun updater was installed as there was an excess of "error 165" messages turning up in the runtime logs. Even though MX7 updater 2 was installed after the jRun installation, it was still using what it considered to be the "latest" jrun version (the one that causes this issue). So the patch was installed and all of a sudden there were no more issues. Probably irrelevant to most of us but its worth taking note, just for anyone thinking of installing jrun updater 6 on a windows 2003 server. Joel -----Original Message----- From: cfaussie@googlegroups.com [mailto:[EMAIL PROTECTED] Behalf Of Charlie Arehart Sent: Thursday, 27 July 2006 1:22 AM To: cfaussie@googlegroups.com Subject: [cfaussie] Re: CFLOCATION Issue Are the client browsers both within the same network? If not, one could be going through a proxy that may be having a problem honoring the redirect that the CFLOCATION causes (some think CFLOCATION sends the users from one page to another on the server, but instead it causes the server to tell the client to go get the other page--a subtle difference). Also, are both clients making the request of the same page running on the same web server? Just seems worth asking, as it could be the web server that's the issue, and you may be testing one against your local server and the other against a remote one. Always best when trying to track down these sort of problems to make sure that all variants are accounted for. Perhaps you have. Just thought I'd throw this in there. /charlie http://www.carehart.org/blog/client/ -----Original Message----- From: cfaussie@googlegroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Joel Cass Sent: Wednesday, July 26, 2006 2:45 AM To: cfaussie@googlegroups.com Subject: [cfaussie] CFLOCATION Issue I have never seen this issue before so I am putting it out there to see if anyone knows what might be happening.. It seems to be an issue with the <cflocation> tag. One computer follows it and the other does not. Two computers, Windows XP, same version of Internet Explorer (6.0.2900.2180.xpsp2_gdr.050301-1519). * One computer follows <cflocation> commands as it should. * The other computer displays the code that appeared before the <cflocation> tag, often an incomplete page or absolutely nothing at all. It does not follow through to the new URL. The server has trusted cache and saved class files turned on. It also has the MX7 updater 2 and JRun 4rc6 installed. It is running in standalone server mode. This is a new issue that just cropped up and I am buggered if I know what is going on.. Any ideas? Thanks --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "cfaussie" group. To post to this group, send email to cfaussie@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cfaussie -~----------~----~----~----~------~----~------~--~---
