>I believe that the HTTP 1.1 specification recommends, but does not >require, that the url, cookie, and form posts be URL encoded. >ColdFusion 4.5.x did not conform to the recommendations, but >ColdFusion 5.0 does. Check the content-type header on the HTTP >Request, I believe its >CONTENT_TYPE=application/x-www-form-urlencoded. > >The workaround is to operate on the name/value pairs with some >implementation of urldecode() on the receiving end.
Yeah, that's always the problem. No control over the receiving end and ColdFusion seems to be the only application that encodes the name portion of the name/value pair. If I could find some spec somewhere that says that the name portion should be encoded, that would be wonderful. -- Bud Schneehagen - Tropical Web Creations, Inc. _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/ Web Based Solutions / eCommerce Development & Hosting http://www.twcreations.com/ - http://www.cf-ezcart.com/ 954.721.3452 - Toll Free: 877.207.6397 - Fax: 954.721.7493 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4 FAQ: http://www.thenetprofits.co.uk/coldfusion/faq This list and all House of Fusion resources hosted by CFHosting.com. The place for dependable ColdFusion Hosting. http://www.cfhosting.com Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
