Recently came across a really bizarre issue with CFHTTP. Look at the code below:
See anything wrong with it? No? Well, here is the output I get:
And no, both the URL's are valid and you can access them through browser or with CFHTTP outside of CFLOOP. Turns out it's a bug in CFHTTP. When CFHTTP is used inside CFLOOP you can't follow an "https" request with "http" request. Huh? Ya, that's what I thought...
I was ready to file a bug report, but before doing that tested it in CF 9 to see what happens and voila, it works!
So, whatever the bug was, it's fixed in CF 9.