> 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. > Woah! I don't know where you got your information from, but according to the HTTP specification data send in the body of GET and POST requests must be encoded. In order to send "raw" (uuencoded) data in a request body you are supposed to use a PUT request. However, the <cfhttp> tag in CF 5 only supports GET and POST requests. On the other hand, CFMX does support sending "raw" requests via <cfhttp> now although it still doesn't support other types of HTTP requests like HEAD.
-Matt ______________________________________________________________________ Your ad could be here. Monies from ads go to support these lists and provide more resources for the community. http://www.fusionauthority.com/ads.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
