Hi, all. I'm afraid that this isn't the problem. The addresses are indeed fully qualified. I have rewritten the CFLOCATION tag several times from scratch to be sure I have no typos. I have cut and pasted the exact URL string from the CFLOCATION url attribute to a browser's address bar (on the server itself) and have successfully reached the site.
Still a mystery... Matthieu -----Original Message----- From: Dave Wilson [mailto:[EMAIL PROTECTED]] Sent: Friday, September 27, 2002 11:29 AM To: CF-Talk Subject: RE: CFLOCATION to external sites - failure Ahhh, cheers Jochem. Then the problem is the client resolving the url's. Well I'd taken it for granted that the url's in the db were all fully qualified, i.e. including http:// etc as Mike had suggested, but it's starting to sound like Mike is correct, unless the client machine is having extraneous networking problems (more unlikely). Dave -----Original Message----- From: Jochem van Dieten [mailto:[EMAIL PROTECTED]] Sent: 27 September 2002 16:22 To: CF-Talk Subject: Re: CFLOCATION to external sites - failure Dave Wilson wrote: > I'm not sure exactly how cflocation works. Whether it (as you say) sends the > redirect instruction to the client, leaving the dns resolution up to the > client machine. Or. It is all handled on the server side. cflocation sends an HTTP 302 "Found" statuscode to the browser together with a header with the new location (see RFC 2616 or the list archive for past discussions). Effectively, it is nothing but: <cfheader statuscode="302"> <cfheader name="location" value="<fully qualified URL>"> Jochem ______________________________________________________________________ Signup for the Fusion Authority news alert and keep up with the latest news in ColdFusion and related topics. http://www.fusionauthority.com/signup.cfm FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
