KT, this is a pretty classic problem. You're trying to run a scheduled task, and it fails. So you grab the URL and run it in a browser, and it works, and you wonder "what is wrong?"
What is wrong is that when you visit the URL in our browser, you benefit from whatever capabilities that browser has (whether built-in or from your having visited the site previously).
But when CF runs the task, note that CF is acting as the browser. It's the same browser that also underlies the CFHTTP tag. if you were o setup a test page that did such a CFHTTP of the URL in question, and then if you dumped the #cfhttp# variable, you'd see similar errors to what you see when you log the output of the task.
And the problem is that the underlying CF browser (the Java httpclient class) does NOT always have the same capabilities as your browser. In this case, your error shows that the page you are visiting (the one doing the cfmail) is held on a web server that is requiring a form of authentication that the httpclient isn't supporting. Or that authentication is expecting additional info that you are not providing in the call to the page.
Notice above I said how your browser may have info from a previous visit to a site. In this case if you visited your site (on which this cfmail page lives) in the past, and that site required you to login (such as with basic authentication), then the browser would remember that username and password and use it in subsequent visits.
But the httpclient browser doesn't remember such things--and you need to tell CF to use a given username and password each time the page is called, whether with the username and password fields in the scheduled task setup, or in a cfhttp call that you make. So first, try adding those.
Second, though, it may be that your web site (hosting that page you're calling) requires "windows authentication", and though cfhttp was said to add NTLM (which some would say is the same thing), I have not had luck with tests of that. I can confirm that as soon as I changed IIS (for a test folder in a test site) to not support "anonymous" authentication and selected another, the error I saw was the same one you saw.
Let us know if you can find more about your web server setup, and whether adding a username/password to your task helps. If not, you may need to consider putting the page (that you want to call) in a folder that has some other form of protection, if you need it (such as only allowing it to be called from the IP of the CF server itself).
Let us know if that helps.
/Charlie (troubleshooter, carehart.org)
13
Replies
AdChoices