Something wrong with MM's Resource xml file?

>It would have been nice to know that Macromedia was changing the path of >their XML file before they actually changed the path.  This would actually >prevent a few websites out there from displaying an XMLParsing() >error.  Not that anyone cares about having their stuff syndicated or anything. > >Just grumbling, >~Todd

What path / url are you using? We did move it, but the old one should still work. mike chambers mesh@macromedia.com > >It would have been nice to know that Macromedia was changing the path of > >their XML file before they actually changed the path.  This would actually > >prevent a few websites out there from displaying an XMLParsing() > >error.  Not that anyone cares about having their stuff syndicated or anything. ----- Excess quoted text cut - see Original Post for more -----

I'll bet folks were using cfhttp and not checking for status code of 302 / 301 and then performing cfhttp again on the redirected location? I posted some code on cf-talk showing how to handle this. We moved it and we put in an Apache redirect. Can someone confirm that is the situation? (the redirect is from /desdev/xxx to /devnet/xxx) On Monday, Mar 10, 2003, at 19:53 US/Pacific, Mike Chambers wrote: ----- Excess quoted text cut - see Original Post for more -----

That is what happened.  My weblog broke temporarily because of it.   Adding the redirect="yes" attribute to cfhttp fixed it. Christian On Tuesday, March 11, 2003, at 01:48 AM, Sean A Corfield wrote: ----- Excess quoted text cut - see Original Post for more -----

Ah, good point! I've blogged a note on it - with a reference to Todd's entry about it. Sorry Todd! On Tuesday, Mar 11, 2003, at 15:32 US/Pacific, Christian Cantrell wrote: > That is what happened.  My weblog broke temporarily because of it. > Adding the redirect="yes" attribute to cfhttp fixed it.

No, I wasn't checking for a status code of 302/301.. and I was using cfhttpd which of course, got me a blank .xml file.  It's partially my fault for not putting a cftry/cfcatch in place to catch the errors, but ... with the sudden relocation of the file, it would have been nice for a warning rather than just putting a redirect in place. Again, just grumbling. ~Todd At 10:48 PM 3/10/2003 -0800, you wrote: ----- Excess quoted text cut - see Original Post for more ----- ---------- Todd Rafferty (todd@web-rat.com) - http://www.web-rat.com/ Team Macromedia Volunteer for ColdFusion http://www.macromedia.com/support/forums/team_macromedia/ http://www.devmx.com/ ----------