> problems with what you're doing is that these authentication schemes > typically keep an auth cookie in the browser. When making an authentication > request from another server, that cookie stays on the requesting entity - the > server itself. You would have to pass the contents of that authentication > cookie from the proxy to the client browser.
Hrmmm... I was actually trying to do something a little different. I did some basic testing passing the Username and Password fields along in the CFHTTP. I was somewhat successful. Basically I got the HTML for the page but then was prompted for a username and password as the page tried to process the CSS, JS and images. My thought was to actually have the "proxy" download those files locally and then change the URL called within the HTML to pull from the saved files instead of the original URL. If I could bypass that by catching the cookie set and forwarding the cookie on to the client's browser it would negate the need to do that... I think. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Create robust enterprise, web RIAs. Upgrade & integrate Adobe Coldfusion MX7 with Flex 2 http://www.adobe.com/products/coldfusion/flex2/?sdid=RVJP Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:274833 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
