> There are two things I can think of off the top of my head, that you > might do. > > First, you might just take a shot in the dark and play with encoding. > You can specify the appropriate encoding for your form post from > CFHTTP using the CHARSET attribute. > > Second, you might want to compare a good request with a bad one - you > can capture HTTP requests on the client using various tools that > record and/or proxy HTTP traffic. You could make a request from a > browser on the same server that's running the CFHTTP tag. > > Dave Watts, CTO, Fig Leaf Software > http://www.figleaf.com/ > http://training.figleaf.com/ > > Fig Leaf Software is a Veteran-Owned Small Business (VOSB) on > GSA Schedule, and provides the highest caliber vendor-authorized > instruction at our training centers, online, or onsi
Thanks Dave. This code hasn't changed in 4 years and it only started "misparsing" the form data when the action page was moved to another server, so this seems like there is an issue with the Coldfusion service on the server. I have the same action page on several different servers. I can change the URL in my CFHTTP and it will work on certain servers and it won't work on other servers. There is no encoding changes or anything, just the URL that the CFHTTP is posting too. This is a CF 5.5 server. Do you think there is a patch that needs to be applied? ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| 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:343182 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
