Sunday, August 4, 2002, 2:19:05 AM, you wrote: >> If so, half your problem is to blame on a Macromedia programmer who >> didn't have his head screwed on right when he decided to urlencode all >> cfhttp posts, and then blame the other programmer who didn't have his >> (could be a her...dunno <g/>) head on straight either when he decided >> it wasn't important when raised during the MX betas. >> I would suggest yelling and screaming at them...don't know if it will >> do any good though. They have ignored the problem forever. They do >> however love to tout the fact that UPS is using CF on their intranet >> in their press releases. Ironic no? >> The other half is that UPS requires text/xml as the Content-Type IIRC, >> another thing cfhttp can't do. >> ML> Woah! I don't know where you got your information from, but according to ML> the HTTP specification data send in the body of GET and POST requests ML> must be encoded. In order to send "raw" (uuencoded) data in a request ML> body you are supposed to use a PUT request. However, the <cfhttp> tag in ML> CF 5 only supports GET and POST requests. On the other hand, CFMX does ML> support sending "raw" requests via <cfhttp> now although it still ML> doesn't support other types of HTTP requests like HEAD.
The specs are not relevant here. I have to send this xml packet to that server and CF4.5 and earlier didn't urlencode it. There is nothing in the spec that says cfhttpparam has to urlencode data instead of the programmer using urlEncodedFormat() around the data either. Which as you may know is how MSXML handles it. It assumes the developers knows what they are doing. That's why this bug when reported during the CF5 betas should have been a relnote bugfix, and not fixed the way it was so CF can no longer talk to all the XML API's that expect http posted xml. I think the raw xml stuff is great, but I personally have never had to integrate with an XML provider that wanted XML that way. It's always been HTTP GET's or POST's. I'd be willing to also bet that a quick poll of the most popular XML API's (UPS, USPS, Ebay, etc) the vast majority use HTTP POST or GET. You can go tell them they are doing it wrong, I don't think they will listen, but if they do, let me know =) -- jon mailto:[EMAIL PROTECTED] ______________________________________________________________________ Signup for the Fusion Authority news alert and keep up with the latest news in ColdFusion and related topics. http://www.fusionauthority.com/signup.cfm FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
