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 ______________________________________________________________________ Your ad could be here. Monies from ads go to support these lists and provide more resources for the community. http://www.fusionauthority.com/ads.cfm 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
