Please send me the HTTP headers and content if you can get it from Firefox using Firebug or HTTPFox
On Thu, Dec 24, 2009 at 12:13 AM, Chen Ding <[email protected]> wrote: > Henry, > > Both use POST, but the messages are different. I am trying to figure out > the differences. > > Chen Ding > > > On Thu, Dec 24, 2009 at 12:42 PM, Henry Minsky > <[email protected]>wrote: > >> Sorry I meant to say that proxied mode always uses a POST request, whereas >> SOLO mode >> can make a GET or a POST request, depending on how you set the querytype >> attribute of the dataset. >> >> 2009/12/23 hminsky <[email protected]> >> >> Can you use a tool like HTTPFox or Firebug to see what the headers are >>> when the data is posted to the server? One difference is that SOLO mode >>> always uses a POST request, whereas SOLO can use a GET request. Might be a >>> different handling by your server of those cases? >>> >>> On Wed, Dec 23, 2009 at 11:36 PM, Chen Ding <[email protected]>wrote: >>> >>>> Henry, >>>> >>>> The problem is on the client side. In the website, there is an edittext >>>> field that collects data (Chinese characters) that are sent to the server. >>>> In the non-deployed version, the data received by the server are correct. >>>> In >>>> the deployed version, however, the data received by the server are >>>> incorrect. >>>> >>>> Thanks! >>>> >>>> Chen Ding >>>> >>>> >>>> On Thu, Dec 24, 2009 at 12:24 PM, Henry Minsky < >>>> [email protected]> wrote: >>>> >>>>> Is the issue with encoding of character data in datasets that you are >>>>> fetching? >>>>> >>>>> >>>>> The issue may be not in the client, but at the server end. The LPS >>>>> server not only proxies data requests, but does character set encoding >>>>> conversion for you as well when it parses the XML. Are you sure that the >>>>> data you are requesting is coming in UTF-8 format from your back-end data >>>>> source? >>>>> >>>>> Flash's XML parser in the Flash player has a very limited repertoire of >>>>> character set encodings >>>>> that it can deal with, so it is best to always send UTF-8 data from >>>>> your server. >>>>> >>>>> >>>>> On Wed, Dec 23, 2009 at 9:46 PM, Chen Ding <[email protected]>wrote: >>>>> >>>>>> Hi There, >>>>>> >>>>>> Merry Christmas! >>>>>> >>>>>> We have a website that works ok. But when we deploy it as solo, it >>>>>> does not support Chinese anymore. We are using the HTML wrapper as below >>>>>> (generated by OpenLaszlo's facility). As I said above, if we run the lzx >>>>>> directly (i.e., USTC.lzx), it works just fine. Is there something we >>>>>> need to >>>>>> specify when convert it to the solo deployment? >>>>>> >>>>>> Thanks! >>>>>> >>>>>> Chen Ding >>>>>> >>>>>> >>>>>> 1 <!DOCTYPE html >>>>>> 2 PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" " >>>>>> http://www.w3.org/TR/html4/loose.dtd"> >>>>>> 3 <html> >>>>>> 4 <head> >>>>>> 5 <meta http-equiv="Content-Type" content="text/html; >>>>>> charset=utf-8"> >>>>>> 6 <link rel="SHORTCUT ICON" href=" >>>>>> http://www.laszlosystems.com/favicon.ico"> >>>>>> 7 <title>Zykie Application</title> >>>>>> 8 <style type="text/css"> >>>>>> 9 html, body { margin: 0; padding: 0; height: >>>>>> 100%; } >>>>>> 10 body { background-color: #eaeaea; } >>>>>> 11 </style> >>>>>> 12 </head> >>>>>> 13 >>>>>> 14 <body> >>>>>> 15 <object type="application/x-shockwave-flash" >>>>>> 16 data=" >>>>>> http://192.168.99.99:8080/lps-4.6.1/prod/Homepages/USTC.lzx.swf8.swf?lzproxied=false >>>>>> " >>>>>> 17 width="100%" height="1500"> >>>>>> 18 <param name="movie" >>>>>> 19 value=" >>>>>> http://192.168.99.99/lps-4.6.1/prod/Homepages/USTC.lzx.swf8.swf?lzproxied=false >>>>>> "/> >>>>>> 20 <param name="quality" value="high"/> >>>>>> 21 <param name="scale" value="noscale"/> >>>>>> 22 <param name="salign" value="LT"/> >>>>>> 23 <param name="menu" value="false"/> >>>>>> 24 <param name="allowFullScreen" value="true"/> >>>>>> 25 </object> >>>>>> 26 </body> >>>>>> 27 </html> >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Henry Minsky >>>>> Software Architect >>>>> [email protected] >>>>> >>>>> >>>>> >>>> >>> >>> >>> -- >>> Henry Minsky >>> Software Architect >>> [email protected] >>> >>> >>> >> >> >> -- >> Henry Minsky >> Software Architect >> [email protected] >> >> >> > -- Henry Minsky Software Architect [email protected]
