OK, so here's an interesting behavior. I'm not saying it's a bug -- that's fightin' words on this list. :)
The cfhttp tag has the resolveurl attribute which will attempt to fully qualify image paths etc in the HTML you are getting. cfhttp also has the redirect attribute that will follow 301 and 302 redirects. Here's the thing though-- Even if ColdFusion follows a redirect, it still uses the original url for the base path to resolve images etc. To show what I mean, create a test file with the following line of code: <cflocation url="http://www.adobe.com";> Then create a second file with the following code: <cfhttp url="HTTP://www.yoursite.com/first_test_file.cfm" method="GET" resolveurl="true" timeout="10"></cfhttp> <cfoutput>#cfhttp.filecontent#</cfoutput> When you visit the second test file in your browser you will see adobie's site, but most of the images are all broken. View the source and you will see that CF resolved all the images, but instead of resolving them to adobe.com it put your website in there since that was the original URL even though it redirected. What do you guys say? Should it do that? I don't think so, but I haven't thought it all the way through yet. ~Brad ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Adobe® ColdFusion® 8 software 8 is the most important and dramatic release to date Get the Free Trial http://ad.doubleclick.net/clk;192386516;25150098;k Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:306944 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
