Load up both pages in firefox and then view info for each. A plain, non-outputting CF page gave me a content-type of utf-8 while a plain, non-outputting htm page gave me a content-type of ISO-8859-1. I think CF automatically returns the generated page using the utf-8 content type.
On Tue, Feb 3, 2009 at 8:29 PM, John Pullam <[email protected]>wrote: > > >Are you defining a base content-type for the page? > > > ><meta http-equiv="Content-type" content="text/html; charset=UTF-8"> > >What about your doctype? > > > > > >On Tue, Feb 3, 2009 at 4:50 PM, John Pullam <[email protected] > >wrote: > > > >> > Here is the Doctype: > > <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" " > http://www.w3.org/TR/html4/strict.dtd";> > > Bear in mind that the 2 pages are identical. The page that works is called > TestPayPal.htm, and the page that doesn't is called TestPayPal.cfm > > The only things I can think of is that the PayPal server is seeing the CFM > and treating it differently. (Or that there is some invisible attribute that > goes along with the page while it is in the client browser and is > subsequently sent to the PayPal server when the FORM Post is executed.) > > There is no other special HTML ... this is pretty vanilla stuff. > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Adobe® ColdFusion® 8 software 8 is the most important and dramatic release to date Get the Free Trial http://ad.doubleclick.net/clk;207172674;29440083;f Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:318818 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
