Hi Rob, Tedious stuff, eh? But I'm not convinced that this isn't a bug.
As far as I can tell, the current (5.0+) versions of IE and Netscape submit form data using whatever encoding is being used to view the form submit page. At least, this has been my emperical experience - I'm not too sure what happens when you do something like submit Japanese characters from an iso-8859-1 encoded page... Does AOLServer perform any implicit silent conversion on received form data? It seems that there must be a way to correct the modification that's happening to the data, since AOLServer undoes whatever it's doing when it ships the data back out to the client. thomas --- Rob Mayoff <[EMAIL PROTECTED]> wrote: > > And HTTP and HTML are weak when it comes to specifying character > sets. > When you submit a form using the GET method, it has to put the form > data > in the URL. But what encoding should it use? As I recall, there's no > way > for the server to ask the client to use a specific charset, and no > way > for the client to tell the server what it used. > ... > +---------- On May 9, atfrost said: > > I posted a few days ago regarding some problems I was having using > > data received by AOLServer via form submission in certain charsets. __________________________________________________ Do You Yahoo!? Yahoo! Shopping - Mother's Day is May 12th! http://shopping.yahoo.com
