Paul, good thoughts. We had thought of both of these, and did our best to eliminate the zoo of encodings by creating a test document that causes the same behavior.
True, I can't be certain that every case that is failing is valid utf-8, but my main test document is one I created in Notepad and saved as utf-8. Zero-byte characters are also possible (though in my test document I don't believe so), but I don't think that would fit the scenario. CF isn't choking on the character I remove, but well after it. CF would choke at the zero-byte character, if there were one, right? On Wed, May 18, 2011 at 1:01 PM, Paul Hastings <p...@sustainablegis.com>wrote: > > On 5/18/2011 10:35 PM, morgan l wrote: > > characters, Greek letters etc). As far as I can tell, all the characters > are > > valid utf-8, but the cfhttp call fails with "Connection Failure" in the > > how do you know that these are valid UTF-8? if plain folks are uploading > them, > chances are you've got a zoo of page encodings. > > any chance there's a zero byte in there some place? cf's never liked those. > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:344684 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
